details: http://hg.nginx.org/nginx/rev/5483d9e77b32
branches:
changeset: 5411:5483d9e77b32
user: Maxim Dounin mdou...@mdounin.ru
date: Wed Oct 02 15:07:17 2013 +0400
description:
Limit req: fixed nodelay parsing.
Previously arguments starting with nodelay were considered valid,
e.g.
details: http://hg.nginx.org/nginx/rev/16b68c724438
branches:
changeset: 5410:16b68c724438
user: Maxim Dounin mdou...@mdounin.ru
date: Wed Oct 02 15:07:15 2013 +0400
description:
Upstream: fixed down and backup parsing.
Previously arguments starting with down or backup were
Hello!
On Wed, Oct 02, 2013 at 03:03:18PM +0300, Anatoli Marinov wrote:
Hello,
Is there an easy way to configure nginx upstream to follow 302 instead of
send them to the browser?
The question seems to be off-topic on the nginx-devel@ list.
The answer is yes, but you'll need to configure it
If we have multiple keyfiles - I like the idea of marking some key as
default.
On Wed, Oct 2, 2013 at 12:47 PM, Piotr Sikora pi...@cloudflare.com wrote:
Hello Maxim,
As previously noted, the patch description is wrong. It also
make sense to add some description of the directive added.
