Specifically I was writing that clients could get their cookies, but not
served form the nginx cache. This has always been about whether or not the
cached page was serving the cookies or not.
With the exact same configuration for the cache, there is a difference
between:
location /
and
locatio
So I found a solution and it seems like there is unexpected behavior from
nginx. proxy_hide_header Set-Cookie does not seem to work when the location
block is set to /
So:
location / {
#Lots of other proxy stuff here..
proxy_hide_header "Set-Cookie"; }
does not allow a cookie to
Indeed, but that prevents all cookies from being set. What I am looking for
is to have a cache hit, but have the set-cookie served from the origin
server. In Apache httpd cache, this can be accomplished with
CacheIgnoreHeaders Set-Cookie.
The back end server here is Apache and I have tried settin
Thanks for the info. I have removed the redundant config. I suppose what I
am really getting at is that I would like Set-Cookie to never be cached with
a cache MISS so that the cached cookie values are then not there for
subsequent HITS.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,2
I am trying to cache the home page to a site. I am only caching the home
page. If I put in a condition to check for cookies existing before caching,
everything works as expected, but there is a high BYPASS rate due to the
client not having the cookies the first time they visit the site. Once I
took
