details: http://hg.nginx.org/nginx/rev/d7a2729623d3
branches:
changeset: 5408:d7a2729623d3
user: Sergey Kandaurov
date: Wed Oct 02 11:50:56 2013 +0400
description:
Version bump.
diffstat:
src/core/nginx.h | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diffs (14 lines
details: http://hg.nginx.org/nginx/rev/11599a3d0c7c
branches:
changeset: 5409:11599a3d0c7c
user: Sergey Kandaurov
date: Wed Oct 02 11:51:04 2013 +0400
description:
Unused macro and variable removed.
The macro NGX_HTTP_DAV_COPY_BLOCK is not used since 8101d9101ed8 (0.8.9).
The variab
Hello Maxim,
> As previously noted, the patch description is wrong. It also
> make sense to add some description of the directive added.
Yeah, will do.
> This makes the directive unavailable without any meaningfull
> diagnostics if nginx was build with old OpenSSL, which isn't very
> user-frien
Hello!
On Tue, Oct 01, 2013 at 05:37:34PM +0400, kyprizel wrote:
> Ok, I don't insist - I just need the functionality. What should I do to get
> my patch accepted? :)
Piotr's patch is already under review, and I don't think that
duplicating efforts make sense. You may want to join the review
details: http://hg.nginx.org/nginx/rev/5483d9e77b32
branches:
changeset: 5411:5483d9e77b32
user: Maxim Dounin
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. "limit_req ...
details: http://hg.nginx.org/nginx/rev/16b68c724438
branches:
changeset: 5410:16b68c724438
user: Maxim Dounin
date: Wed Oct 02 15:07:15 2013 +0400
description:
Upstream: fixed "down" and "backup" parsing.
Previously arguments starting with "down" or "backup" were considered
valid, e
Hello,
Is there an easy way to configure nginx upstream to follow 302 instead of
send them to the browser?
Thanks
___
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel
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 i
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 wrote:
> Hello Maxim,
>
> > As previously noted, the patch description is wrong. It also
> > make sense to add some description of the directive added.
>
> Yeah, will do
