Re: IPv6 support in resolver

2013-10-30 Thread Maxim Dounin
Hello! On Tue, Oct 29, 2013 at 04:06:35PM +0400, ToSHiC wrote: > Hello, > > Yesterday you had a talk on Highload++ and said about lack of IPv6 resolver > support. Do you have any news about my patch? Just in case, it was me who had a talk, there are lots of Maxim's here. ;) Ruslan Ermilov, wh

Re: [PATCH] Make $proxy_host and $proxy_port accessible in dynamic languages

2013-10-30 Thread Maxim Dounin
Hello! On Mon, Oct 28, 2013 at 02:44:45PM -0700, Yichun Zhang (agentzh) wrote: > Hello! > > On Mon, Oct 28, 2013 at 1:41 PM, Maxim Dounin wrote: > > > > What's the intended use? > > I cannot really speak for my user. But one use case that I can think > of is for (nonblocking) access logging in

[nginx] Core: apply missed options to sockets added during binar...

2013-10-30 Thread Maxim Dounin
details: http://hg.nginx.org/nginx/rev/d8ee8ef5dcde branches: changeset: 5430:d8ee8ef5dcde user: Piotr Sikora date: Thu Oct 24 14:18:37 2013 -0700 description: Core: apply missed options to sockets added during binary upgrade. The accept_filter and deferred options were not applied

[nginx] Core: handling of getsockopt(TCP_DEFER_ACCEPT) failures.

2013-10-30 Thread Maxim Dounin
details: http://hg.nginx.org/nginx/rev/91bd62a9627e branches: changeset: 5431:91bd62a9627e user: Maxim Dounin date: Thu Oct 31 04:00:37 2013 +0400 description: Core: handling of getsockopt(TCP_DEFER_ACCEPT) failures. Recent Linux versions started to return EOPNOTSUPP to getsockopt()

Re: [PATCH] Core: apply missed options to sockets added during binary upgrade.

2013-10-30 Thread Maxim Dounin
Hello! On Thu, Oct 24, 2013 at 02:22:05PM -0700, Piotr Sikora wrote: > # HG changeset patch > # User Piotr Sikora > # Date 1382649517 25200 > # Thu Oct 24 14:18:37 2013 -0700 > # Node ID d8ee8ef5dcde554bf1d89d61912e6e6f3c5573f2 > # Parent e6a1623f87bc96d5ec62b6d77356aa47dbc60756 > Core: ap

Re: [PATCH] Core: stop trying to get TCP_DEFER_ACCEPT from unix sockets.

2013-10-30 Thread Maxim Dounin
Hello! On Mon, Oct 28, 2013 at 02:16:48PM -0700, Piotr Sikora wrote: > Hey Maxim, > > > Ok, fair enough. Wouldn't something like this be better then > > (untested)? > > It would, originally I had pretty much the same patch, but for some > reason I thought you'd like the one I send better. > >

Re: [PATCH] ngx_gzip might hang the request for slow downstreams

2013-10-30 Thread Maxim Dounin
Hello! On Mon, Oct 28, 2013 at 03:37:44PM -0700, Yichun Zhang (agentzh) wrote: > Hello! > > On Mon, Oct 28, 2013 at 2:02 PM, Maxim Dounin wrote: > >> > >> -if (ctx->nomem) { > >> +if (ctx->nomem || in == NULL) { > >> > >> /* flush busy buffers */ > > > > Is the same problem exis

[nginx] Gzip, gunzip: flush pending data when incoming chain is ...

2013-10-30 Thread Maxim Dounin
details: http://hg.nginx.org/nginx/rev/c52a761a2029 branches: changeset: 5432:c52a761a2029 user: Yichun Zhang date: Mon Oct 28 15:01:36 2013 -0700 description: Gzip, gunzip: flush pending data when incoming chain is NULL. diffstat: src/http/modules/ngx_http_gunzip_filter_module.c

[nginx] Removed extra allocation for $sent_http_last_modified.

2013-10-30 Thread Maxim Dounin
details: http://hg.nginx.org/nginx/rev/c21e341c51cb branches: changeset: 5434:c21e341c51cb user: Maxim Dounin date: Thu Oct 31 04:02:59 2013 +0400 description: Removed extra allocation for $sent_http_last_modified. There is no need to allocate memory for "Last-Modified: " string, th

[nginx] Auth basic: "info" logging level on no user/password.

2013-10-30 Thread Maxim Dounin
details: http://hg.nginx.org/nginx/rev/c37f34bda5ea branches: changeset: 5433:c37f34bda5ea user: Maxim Dounin date: Thu Oct 31 04:02:21 2013 +0400 description: Auth basic: "info" logging level on no user/password. This isn't an exceptional condition and normally happens on first req

[nginx] Gunzip: proper error handling on gunzipping an empty res...

2013-10-30 Thread Maxim Dounin
details: http://hg.nginx.org/nginx/rev/6aa75f4982ce branches: changeset: 5436:6aa75f4982ce user: Maxim Dounin date: Thu Oct 31 04:16:20 2013 +0400 description: Gunzip: proper error handling on gunzipping an empty response. With previous code, an empty (malformed) response resulted i

[nginx] Gunzip: "error" logging level on inflate() errors.

2013-10-30 Thread Maxim Dounin
details: http://hg.nginx.org/nginx/rev/2bb2571d6e34 branches: changeset: 5435:2bb2571d6e34 user: Maxim Dounin date: Thu Oct 31 04:12:53 2013 +0400 description: Gunzip: "error" logging level on inflate() errors. Errors can easily happen due to broken upstream responses, there is no n