Failing to cache requests
Andrei
lagged at gmail.com
Sun Sep 22 14:37:51 UTC 2019
Hello,
Thanks for the confirmation! Is there a way to selectively ignore only
specific "set-cookie"/cookies, versus all "set-cookie" headers to force
cache? Or even better to remove/strip certain cookies with a regex match? I
imagine this way I can strip the cookies that aren't relevant, it would
cache on it's own, and if some new cookie appears it will avoid caching the
request. I believe this might be doable using Lua, but I haven't had any
luck :(
On Sun, Sep 22, 2019 at 7:26 AM Francis Daly <francis at daoine.org> wrote:
> On Sat, Sep 21, 2019 at 01:02:57PM -0500, Andrei wrote:
>
> Hi there,
>
> > I'm having a hard time understanding why these requests aren't being
> cached
> > for 10 minutes? Is it the cookies?
>
> Yes.
>
> http://nginx.org/r/proxy_cache_valid
>
> """
> If the header includes the “Set-Cookie” field, such a response will not be
> cached.
> """
>
> > If so how can I avoid this and force cache?
>
> """
> Processing of one or more of these response header fields can be disabled
> using the proxy_ignore_headers directive.
> """
>
> f
> --
> Francis Daly francis at daoine.org
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20190922/a5a54ef5/attachment.htm>
More information about the nginx
mailing list