since 0.7.48 and the fact that headers like Expires or Cache-Control
are take into account … I’m not able to cache everything. If the
backend set a Expires header in the past, then the page is never
cached. Is there a way to make it work like this ?
Thanks
have access to the backend code and no one can
The patch is attached. I’ve tested it with proxy but not with fastcgi.
As the patch is simple, it should not be a problem.
Hope it would help.
Thank you for the patch, however, I’m going to implement more generic
directive proxy/fastcgi_ignore_header to ignore as well X-Accel-Redirect,
X-Accel-Expires, etc.
OK, I’ll use my patch the time this feature is realeased. I juste
wanted to be sure that in the near future all my architecture with
nginx will still be valid
On Wed, Apr 29, 2009 at 02:03:06AM +0200, J?r?me Loyet wrote:
The patch is attached. I’ve tested it with proxy but not with fastcgi.
As the patch is simple, it should not be a problem.
Hope it would help.
Thank you for the patch, however, I’m going to implement more generic
directive proxy/fastcgi_ignore_header to ignore as well
X-Accel-Redirect,
X-Accel-Expires, etc.
just adds an extra macro/function in there to do an nginx -t
$conffile, and adds it in appropriate places (reload, restart, start,
now upgrade as well)
however, i suppose depending on the signal that “stop” sends it could
be done a lot quicker (restart should force stop, which is the -QUIT i
believe?) we had issues where it seemed like sockets weren’t cleaned
up fast enough or something.