[nginx] Upstream: proxy_limit_rate and friends.

details: http://hg.nginx.org/nginx/rev/973ee2276300 branches: changeset: 5883:973ee2276300 user: Roman Arutyunyan date: Tue Oct 28 12:29:59 2014 +0300 description: Upstream: proxy_limit_rate and friends. The directives limit the upstream read rate. For example, "proxy_limit_rate 42

[nginx] Write filter: stored delay in a variable, no functional ...

details: http://hg.nginx.org/nginx/rev/8486205d10db branches: changeset: 5884:8486205d10db user: Roman Arutyunyan date: Tue Oct 28 12:29:59 2014 +0300 description: Write filter: stored delay in a variable, no functional changes. The code is now similar to ngx_event_pipe_read_upstrea

[nginx] Core: added limit to recv_chain().

details: http://hg.nginx.org/nginx/rev/ec81934727a1 branches: changeset: 5882:ec81934727a1 user: Roman Arutyunyan date: Tue Oct 28 12:29:58 2014 +0300 description: Core: added limit to recv_chain(). diffstat: src/event/ngx_event_openssl.c| 19 +++ src/event/ng

[nginx] Upstream: limited next_upstream time and tries when reso...

details: http://hg.nginx.org/nginx/rev/5a042519bfe7 branches: changeset: 5885:5a042519bfe7 user: Gu Feng date: Mon Oct 27 19:52:03 2014 +0800 description: Upstream: limited next_upstream time and tries when resolving DNS. When got multiple upstream IP addresses using DNS resolving,

Re: SIGHUP and ngx_module_t

Hello! On Tue, Oct 28, 2014 at 08:30:15AM +0200, Donatas Abraitis wrote: > Hello, > > is it true, that SIGHUP is not handled by ngx_module_t /* exit process */ ? > > I mean if I have these defined: > > ngx_http_modsecurity_terminate, /* exit process */ > ngx_http_modsecurity_terminate,

Re: [PATCH] Upstream: limited next_upstream time and tries when resolving DNS

On 27 Oct 2014, at 14:53, Gu Feng wrote: > # HG changeset patch > # User Gu Feng > # Date 1414410723 -28800 > # Mon Oct 27 19:52:03 2014 +0800 > # Node ID ccc3b86835da54273c333e7d6a00f68e0b0e6c27 > # Parent 973fded4f461f3a397779b3a1dc80881b1b34974 > Upstream: limited next_upstream time an

Re: [PATCH] Support cross compiling with MinGW-w64 on Debian GNU/Linux

Hi, In <20141027174711.gd45...@mdounin.ru> "Re: [PATCH] Support cross compiling with MinGW-w64 on Debian GNU/Linux" on Mon, 27 Oct 2014 20:47:11 +0300, Maxim Dounin wrote: > - the NGX_GNUC_64 macro was removed, __MINGW64_VERSION_MAJOR > tested directly instead; > > - the #include <_ming

[nginx] Win32: made build-able with MinGW-w64 gcc.

details: http://hg.nginx.org/nginx/rev/5d4e4619982f branches: changeset: 5886:5d4e4619982f user: Kouhei Sutou date: Wed Oct 15 21:15:01 2014 +0900 description: Win32: made build-able with MinGW-w64 gcc. diffstat: src/os/win32/ngx_win32_config.h | 37 ++

Re: [PATCH] Support cross compiling with MinGW-w64 on Debian GNU/Linux

Hello! On Tue, Oct 28, 2014 at 10:04:00PM +0900, Kouhei Sutou wrote: > Hi, > > In <20141027174711.gd45...@mdounin.ru> > "Re: [PATCH] Support cross compiling with MinGW-w64 on Debian GNU/Linux" on > Mon, 27 Oct 2014 20:47:11 +0300, > Maxim Dounin wrote: > > > - the NGX_GNUC_64 macro was re

Re: [PATCH] SPDY: stop emitting empty header values

On Monday 27 October 2014 14:33:15 Piotr Sikora wrote: > # HG changeset patch > # User Piotr Sikora > # Date 1414445156 25200 > # Mon Oct 27 14:25:56 2014 -0700 > # Node ID e590d484a7f9d2750e2cd45ea16c601ae01cb607 > # Parent ee9230cd4bda9f9e7e83f7baf37d66ad6bb9b0c1 > SPDY: stop emitting empt

Re: [PATCH] Support cross compiling with MinGW-w64 on Debian GNU/Linux

Hi, In <20141028133802.gl45...@mdounin.ru> "Re: [PATCH] Support cross compiling with MinGW-w64 on Debian GNU/Linux" on Tue, 28 Oct 2014 16:38:02 +0300, Maxim Dounin wrote: >> > - the NGX_GNUC_64 macro was removed, __MINGW64_VERSION_MAJOR >> > tested directly instead; >> > >> > - the #in

[PATCH] Add Win32 related files into tar.gz

Hi, The current nginx can be built with MinGW-w64. Could you add Win32 related files into tar.gz? If tar.gz includes Win32 related file, I can build nginx for Windows from tar.gz. Thanks, -- kou # HG changeset patch # User Kouhei Sutou # Date 1414505796 -32400 # Tue Oct 28 23:16:36 2014 +0

[nginx] Updated OpenSSL used for win32 builds.

details: http://hg.nginx.org/nginx/rev/e40ce16b2c42 branches: changeset: 5887:e40ce16b2c42 user: Maxim Dounin date: Tue Oct 28 17:35:00 2014 +0300 description: Updated OpenSSL used for win32 builds. diffstat: misc/GNUmakefile | 2 +- 1 files changed, 1 insertions(+), 1 deletions(

[nginx] nginx-1.7.7-RELEASE

details: http://hg.nginx.org/nginx/rev/6d2fbc30f8a7 branches: changeset: 5888:6d2fbc30f8a7 user: Maxim Dounin date: Tue Oct 28 18:04:46 2014 +0300 description: nginx-1.7.7-RELEASE diffstat: docs/xml/nginx/changes.xml | 110 + 1 files ch

[nginx] release-1.7.7 tag

details: http://hg.nginx.org/nginx/rev/0103dc197a90 branches: changeset: 5889:0103dc197a90 user: Maxim Dounin date: Tue Oct 28 18:04:46 2014 +0300 description: release-1.7.7 tag diffstat: .hgtags | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diffs (8 lines): diff --gi

Re: nginx-devel Digest, Vol 60, Issue 34

last = ngx_cpymem(last, h[j].value.data, h[j].value.len); > > +last = ngx_cpymem(last, h[j].value.data, > h[j].value.len); > > +} > > > > h[j].hash = 2; > > } > > > > > Ok. Ruslan? Maxim? Will yo

Re: nginx-devel Digest, Vol 60, Issue 34

Hello! On Tue, Oct 28, 2014 at 05:22:38PM +0200, Donatas Abraitis wrote: By replying to digests, you ask everyone to not answer. Please don't do this. [...] -- Maxim Dounin http://nginx.org/ ___ nginx-devel mailing list nginx-devel@nginx.org http:

Re: [PATCH] Add Win32 related files into tar.gz

Hello! On Tue, Oct 28, 2014 at 11:19:17PM +0900, Kouhei Sutou wrote: > Hi, > > The current nginx can be built with MinGW-w64. Could you add > Win32 related files into tar.gz? If tar.gz includes Win32 > related file, I can build nginx for Windows from tar.gz. I would rather not. They are omitte

Re: [nginx] Cache: multiple variants of a resource now can be stored.

On Mon, Oct 27, 2014 at 06:20:13PM +, Maxim Dounin wrote: > details: http://hg.nginx.org/nginx/rev/78c49e243848 > branches: > changeset: 5880:78c49e243848 > user: Maxim Dounin > date: Mon Oct 27 21:14:10 2014 +0300 > description: > Cache: multiple variants of a resource now can b

[nginx] Version bump.

details: http://hg.nginx.org/nginx/rev/049c3ea24480 branches: changeset: 5890:049c3ea24480 user: Valentin Bartenev date: Tue Oct 28 21:58:49 2014 +0300 description: Version bump. diffstat: src/core/nginx.h | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diffs (14 line

[nginx] SPDY: stop emitting multiple empty header values.

details: http://hg.nginx.org/nginx/rev/87ada3ba1392 branches: changeset: 5891:87ada3ba1392 user: Piotr Sikora date: Mon Oct 27 14:25:56 2014 -0700 description: SPDY: stop emitting multiple empty header values. Previously, nginx would emit empty values in a header with multiple, NULL

Re: [PATCH] SPDY: stop emitting empty header values

On Monday 27 October 2014 14:33:15 Piotr Sikora wrote: > # HG changeset patch > # User Piotr Sikora > # Date 1414445156 25200 > # Mon Oct 27 14:25:56 2014 -0700 > # Node ID e590d484a7f9d2750e2cd45ea16c601ae01cb607 > # Parent ee9230cd4bda9f9e7e83f7baf37d66ad6bb9b0c1 > SPDY: stop emitting empt

Re: [nginx] Cache: multiple variants of a resource now can be stored.

On Tue, Oct 28, 2014 at 10:01:19PM +0400, Ruslan Ermilov wrote: > On Mon, Oct 27, 2014 at 06:20:13PM +, Maxim Dounin wrote: > > details: http://hg.nginx.org/nginx/rev/78c49e243848 > > branches: > > changeset: 5880:78c49e243848 > > user: Maxim Dounin > > date: Mon Oct 27 21:14:10

Re: [nginx] Updated OpenSSL used for win32 builds.

Hey Maxim, > Updated OpenSSL used for win32 builds. Uhm, committing this before merging my patch [1] broke password-protected private keys (using multiple passwords in the same ssl_password_file feature) on win32 for the 1.7.7 release. [1] http://mailman.nginx.org/pipermail/nginx-devel/2014-Octo