# HG changeset patch
# User Gu Feng
# Date 1414394704 -28800
# Mon Oct 27 15:25:04 2014 +0800
# Node ID a7d62f0f3000d156477f556e5cb307f229fe6301
# Parent 973fded4f461f3a397779b3a1dc80881b1b34974
Upstream: limited next_upstream time and tries when resolving DNS.
When got multiple upstream IP
On Mon, Oct 27, 2014 at 03:27:03PM +0800, Gu Feng wrote:
> # HG changeset patch
> # User Gu Feng
> # Date 1414394704 -28800
> # Mon Oct 27 15:25:04 2014 +0800
> # Node ID a7d62f0f3000d156477f556e5cb307f229fe6301
> # Parent 973fded4f461f3a397779b3a1dc80881b1b34974
> Upstream: limited next_ups
# 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 and tries when resolving DNS.
When got multiple upstream IP
On Oct 24, 2014, at 3:29 PM, Piotr Sikora wrote:
> # HG changeset patch
> # User Piotr Sikora
> # Date 1414150080 25200
> # Fri Oct 24 04:28:00 2014 -0700
> # Node ID f71b843694fc2be7eabb9313aa82fb87e83210d6
> # Parent 973fded4f461f3a397779b3a1dc80881b1b34974
> SSL: make ssl_password_file w
On Tuesday 21 October 2014 04:16:01 Piotr Sikora wrote:
> # HG changeset patch
> # User Piotr Sikora
> # Date 1413890111 25200
> # Tue Oct 21 04:15:11 2014 -0700
> # Node ID fbc2eb84bd266b64644b00a6454c4f79f241af5a
> # Parent 973fded4f461f3a397779b3a1dc80881b1b34974
> SPDY: stop emitting emp
Hello!
On Sat, Oct 25, 2014 at 09:27:39AM -0700, W. Trevor King wrote:
> The patch successfully passes through error codes, but I haven't been
> able to find a way to distinguish between auth-endpoint errors and
> errors from the authorized endpoint. For example, with:
>
> location = /auth {
Hi,
Could you confirm the patch?
http://mailman.nginx.org/pipermail/nginx-devel/2014-October/006094.html
Thanks,
--
kou
In <20141018.004250.1469014097857676892@cozmixng.org>
"Re: [PATCH] Support cross compiling with MinGW-w64 on Debian GNU/Linux" on
Sat, 18 Oct 2014 00:42:50 +0900 (JS
Hello!
On Mon, Oct 27, 2014 at 04:55:28PM +0300, Sergey Kandaurov wrote:
> On Oct 24, 2014, at 3:29 PM, Piotr Sikora wrote:
> > # HG changeset patch
> > # User Piotr Sikora
> > # Date 1414150080 25200
> > # Fri Oct 24 04:28:00 2014 -0700
> > # Node ID f71b843694fc2be7eabb9313aa82fb87e83210
Hello!
On Tue, Oct 28, 2014 at 12:01:26AM +0900, Kouhei Sutou wrote:
> Hi,
>
> Could you confirm the patch?
>
> http://mailman.nginx.org/pipermail/nginx-devel/2014-October/006094.html
Sorry, I have been travelling to the nginx.conf conference and
wasn't yet able to review the patch. Below
details: http://hg.nginx.org/nginx/rev/c525c0454aa5
branches:
changeset: 5879:c525c0454aa5
user: Maxim Dounin
date: Mon Oct 27 21:14:07 2014 +0300
description:
Cache: c->reading flag introduced.
It replaces c->buf in checks in ngx_http_file_cache_open(), making it possible
to reopen
details: http://hg.nginx.org/nginx/rev/2c89956b6a76
branches:
changeset: 5878:2c89956b6a76
user: Maxim Dounin
date: Mon Oct 27 21:13:58 2014 +0300
description:
Cache: hash of Vary headers now stored in cache.
To cache responses with Vary, we now calculate hash of headers listed
in V
details: http://hg.nginx.org/nginx/rev/60fde1bc7236
branches:
changeset: 5877:60fde1bc7236
user: Maxim Dounin
date: Mon Oct 27 21:13:39 2014 +0300
description:
Cache: disable caching of responses with Vary (ticket #118).
The "proxy_ignore_header" directive now undersands the "Vary"
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 be stored.
If a variant stored can't be used to respond to a request, the va
details: http://hg.nginx.org/nginx/rev/ee9230cd4bda
branches:
changeset: 5881:ee9230cd4bda
user: Maxim Dounin
date: Mon Oct 27 21:14:12 2014 +0300
description:
Cache: normalization of some Vary headers.
Spaces in Accept-Charset, Accept-Encoding, and Accept-Language headers
are now i
Hey Valentin.
> IMHO, there is no need to introduce "sep" variable:
I think you're right, thanks!
Best regards,
Piotr Sikora
___
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel
# 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 empty header values.
Previously, nginx would emit empty values in a head
Hey Maxim,
> Is OPENSSL_IS_BORINGSSL part also needs changes for PKCS12?
I'm pretty sure it does, I'll take care of it shortly.
Also, I think that PKCS#12 support should be added in a separate
commit, instead of mixing it with semi-related fix.
Best regards,
Piotr Sikora
__
Hey Sergey,
> diff -r 973fded4f461 -r 8c59ef63e7c0 src/event/ngx_event_openssl.h
> --- a/src/event/ngx_event_openssl.h Wed Oct 15 22:57:23 2014 +0400
> +++ b/src/event/ngx_event_openssl.h Mon Oct 27 13:19:01 2014 +0300
> @@ -22,6 +22,7 @@
> #include
> #endif
> #include
> +#include
>
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, /* exit master */
So, sending SIGHUP to the master it doesn't call the
ngx_http_modsecuri
19 matches
Mail list logo