Nginx-0.7.53

Hi Igor,

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
++ jerome

2009/4/28 Igor S. [email protected]:

2009/4/29 Igor S. [email protected]:

Thanks
have access to the backend code and no one can :frowning:

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 :slight_smile:

Thx a lot igor
++ Jerome

FWIW, I updated my init script for nginx to be able to do upgrades…

–Jauder

Michael S. wrote:

the wiki is out of date then. it says USR2 then WINCH. not WINCH then
QUIT.

So there is no USR2 required? I will update the wiki with these
instructions (is there a version this started in?)

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.

you should add in the config file checks using-t like cliff has with
his redhat script (was it cliff?)

that’s an awesome feature. if it fails config check it wont reload or
restart etc.

Do you have a link to this?

Michael S. wrote:

you should add in the config file checks using-t like cliff has with
his redhat script (was it cliff?)

that’s an awesome feature. if it fails config check it wont reload or
restart etc.

basically this:

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)

also we had to add in a sleep inside of restart

restart() {
configtest || return $?
stop
sleep 3
start
}

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.