Everything is fastcgi, my question is how best to treat one single fastcgi
URL differently (caching it instead of forwarding every request to the
backend).
On Wed, Jun 24, 2015 at 12:37 PM, ryd994 wrote:
>
>
> On Tue, Jun 23, 2015 at 6:27 PM CJ Ess wrote:
>
>> So looks like your saying the bes
On Tue, Jun 23, 2015 at 6:27 PM CJ Ess wrote:
> So looks like your saying the best way to do it is to do a separate
> location and duplicate the fastcgi setup in that location and add the
> fastcgi_cache stuff.
>
> I can work with that, however I came across this example while googling (
> https:
On Tue, Jun 23, 2015 at 06:27:30PM -0400, CJ Ess wrote:
Hi there,
> So looks like your saying the best way to do it is to do a separate
> location and duplicate the fastcgi setup in that location and add the
> fastcgi_cache stuff.
It strikes me as clearer to have one extra location{} than to hav
So looks like your saying the best way to do it is to do a separate
location and duplicate the fastcgi setup in that location and add the
fastcgi_cache stuff.
I can work with that, however I came across this example while googling (
https://gist.github.com/magnetikonline/10450786) that uses "if" t
On Tue, Jun 23, 2015 at 04:19:48PM -0400, CJ Ess wrote:
Hi there,
> - Would I need to define a separate location stanza for the URL I want to
> cache and duplicate all of the fastcgi configuration that is normally
> required? Or is there a way to indicate that of all the fastcgi requests
> only t
Hello,
I am looking for advice. I am using nginx to terminate SSL and forward the
request to php via fastcgi. Of all of requests I am forwarding to fastcgi
there is one particular URL that I want to cache, hopefully bypassing
communication with the fastcgi and php processes altogether.
- Would I
