On Thu, Feb 08, 2018 at 08:45:50AM -0500, beatnut wrote: > Hi everyone, > According to the roadmap https://trac.nginx.org/nginx/roadmap server push > will show up in a few days. It's been committed today and will be available in the next release. > My question is : > How to mitigate problem when we are pushing resources already being in the > cache for example pushed earlier ?by ru@nginx.com - Nginx Mailing List - English
On Thu, Feb 08, 2018 at 05:07:49PM +0000, Alessandro Ghedini wrote: > On Thu, Feb 08, 2018 at 05:04:58PM +0000, Alessandro Ghedini wrote: > > # HG changeset patch > > # User Alessandro Ghedini <alessandro@cloudflare.com> > > # Date 1518109032 0 > > # Thu Feb 08 16:57:12 2018 +0000 > > # Branch push-copy-headers > > # Node ID 4f7f42e6d13add2ab0c7a96by ru@nginx.com - Nginx Development
details: http://hg.nginx.org/nginx/rev/a49af443656f branches: changeset: 7202:a49af443656f user: Ruslan Ermilov <ru@nginx.com> date: Thu Feb 08 12:11:30 2018 +0300 description: HTTP/2: fixed build with -Werror=unused-but-set-variable. diffstat: src/http/v2/ngx_http_v2_filter_module.c | 13 +++---------- 1 files changed, 3 insertions(+), 10 deletions(-) diffs (33 lines): dby ru@nginx.com - Nginx Development
details: http://hg.nginx.org/nginx/rev/641306096f5b branches: changeset: 7201:641306096f5b user: Ruslan Ermilov <ru@nginx.com> date: Thu Feb 08 09:55:03 2018 +0300 description: HTTP/2: server push. Resources to be pushed are configured with the "http2_push" directive. Also, preload links from the Link response headers, as described in https://www.w3.org/TR/preload/#by ru@nginx.com - Nginx Development
details: http://hg.nginx.org/nginx/rev/cadb43014c7c branches: changeset: 7200:cadb43014c7c user: Ruslan Ermilov <ru@nginx.com> date: Thu Feb 08 09:54:49 2018 +0300 description: HTTP/2: changed prototypes of request pseudo-headers parsers. No functional changes. diffstat: src/http/v2/ngx_http_v2.c | 49 +++++++++++++++++++++++----------------------- 1 files changed, 24 inseby ru@nginx.com - Nginx Development
details: http://hg.nginx.org/nginx/rev/6ba68ad8b24c branches: changeset: 7199:6ba68ad8b24c user: Ruslan Ermilov <ru@nginx.com> date: Thu Feb 08 09:54:18 2018 +0300 description: Basic support of the Link response header. diffstat: src/http/modules/ngx_http_headers_filter_module.c | 42 ++++++++++++---------- src/http/ngx_http_request.h | 1 + src/httpby ru@nginx.com - Nginx Development
On Fri, Feb 02, 2018 at 11:10:57AM -0800, Matthew Marangoni wrote: > # HG changeset patch > # User Matthew Marangoni <matthew.marangoni@gmail.com> > # Date 1516655725 28800 > # Mon Jan 22 13:15:25 2018 -0800 > # Node ID e84b174c99ca39155e80dbb7458181e20190b70b > # Parent cbf59d483c9cd94dc0fb05f1978601d02af69c20 > Optimized murmurhash performance. > > Improveby ru@nginx.com - Nginx Development
details: http://hg.nginx.org/nginx/rev/0b72d545f098 branches: changeset: 7194:0b72d545f098 user: Ruslan Ermilov <ru@nginx.com> date: Tue Jan 30 22:23:58 2018 +0300 description: Upstream: removed X-Powered-By from the list of special headers. After 1e720b0be7ec, it's neither specially processed nor copied when redirecting with X-Accel-Redirect. diffstat: src/http/ngx_http_upby ru@nginx.com - Nginx Development
details: http://hg.nginx.org/nginx/rev/d5a535774861 branches: changeset: 7192:d5a535774861 user: Ruslan Ermilov <ru@nginx.com> date: Tue Jan 30 14:44:31 2018 +0300 description: HTTP/2: finalize request as bad if parsing of pseudo-headers fails. This is in line when the required pseudo-headers are missing, and avoids spurious zero statuses in access.log. diffstat: src/http/vby ru@nginx.com - Nginx Development
details: http://hg.nginx.org/nginx/rev/61d276dcd493 branches: changeset: 7191:61d276dcd493 user: Ruslan Ermilov <ru@nginx.com> date: Mon Jan 29 16:06:33 2018 +0300 description: HTTP/2: more style, comments, and debugging. diffstat: src/http/v2/ngx_http_v2.c | 33 ++- src/http/v2/ngx_http_v2.h | 3 +- src/http/v2/ngx_http_v2_filter_module.c |by ru@nginx.com - Nginx Development
details: http://hg.nginx.org/nginx/rev/e11a0679d349 branches: changeset: 7190:e11a0679d349 user: Ruslan Ermilov <ru@nginx.com> date: Mon Jan 29 15:54:36 2018 +0300 description: HTTP/2: handle duplicate INITIAL_WINDOW_SIZE settings. diffstat: src/http/v2/ngx_http_v2.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diffs (21 lines): diff -r cbf59d483c9c -r e11a0by ru@nginx.com - Nginx Development
details: http://hg.nginx.org/nginx/rev/cbf59d483c9c branches: changeset: 7189:cbf59d483c9c user: Ruslan Ermilov <ru@nginx.com> date: Tue Jan 16 13:52:03 2018 +0300 description: Fixed --test-build-eventport on macOS 10.12 and later. In macOS 10.12, CLOCK_REALTIME and clockid_t were added, but not timer_t. diffstat: src/event/modules/ngx_eventport_module.c | 2 ++ 1 files chby ru@nginx.com - Nginx Development
Hi Gena, On Thu, Dec 28, 2017 at 12:42:25PM +0200, Gena Makhomed wrote: > Hello, All! > > Scanning nginx sources and nginx documentation > I found some directives, which present in nginx sources > but absent in nginx documentation: Internally, we have a document that explains why certain directives are undocumented. > acceptex_read > iocp_threads > post_acceptex + use iby ru@nginx.com - Nginx Development
Hi, On Tue, Dec 12, 2017 at 02:39:31AM +0000, 廖统浪 wrote: > # HG changeset patch > # User Liao Tonglang <liaotonglang@gmail.com> > # Date 1512991389 -28800 > # Mon Dec 11 19:23:09 2017 +0800 > # Node ID 77be99f1a4766bf19761dfcf03531242923bd0a2 > # Parent d3235149d17f7745d3ac246a6cdcc81a56698f7b > Increase size to sizeof(ngx_pool_t) if need when create pool &gby ru@nginx.com - Nginx Development
details: http://hg.nginx.org/nginx/rev/8b84d60ef13d branches: changeset: 7162:8b84d60ef13d user: Ruslan Ermilov <ru@nginx.com> date: Tue Nov 28 12:00:24 2017 +0300 description: Fixed "changing binary" when reaper is not init. On some systems, it's possible that reaper of orphaned processes is set to something other than "init" process. On such systems, theby ru@nginx.com - Nginx Development
On Mon, Nov 20, 2017 at 02:59:39AM -0500, hook wrote: > Hi > I'm writing some module with using ngx_write_file. I found file's > offset is incorrect, in this case: > ``` > u_char av = 0x01 | 0x04; > // file cur offset -> 4096; > ngx_write_file(file, &av, 1, 4) > ``` > file->offset would be 4097, but real offset is 4096. file->by ru@nginx.com - Nginx Mailing List - English
details: http://hg.nginx.org/nginx/rev/595a3de03e91 branches: changeset: 7154:595a3de03e91 user: Ruslan Ermilov <ru@nginx.com> date: Thu Nov 16 13:20:47 2017 +0300 description: Xslt: fixed parameters parsing (ticket #1416). If parameters were specified in xslt_stylesheet without variables, any request except the first would cause an internal server error. diffstat: src/httpby ru@nginx.com - Nginx Development
Hi, On Wed, Nov 15, 2017 at 09:57:28PM +0100, Karim Malhas wrote: > Hi all, > > I recently discovered a bug [0] concerning the xslt_stylesheet directive as > documented here [1]. > > The root cause of this issue is that the parser of the directive also > modifies it instead of just reading it. > > I have created a patch which lets the parser work on a copy of that &by ru@nginx.com - Nginx Development
On Wed, Nov 08, 2017 at 10:00:44PM +0800, 洪志道 wrote: > Thank you for your reply. > > What I want to solve is that backup servers can be selected when all the > primary servers are unavailable. > > Now I use error_page to solve it, but it's not convenient in the case of > multi-servers-locations. > Especially some locations have already config error_page directive. &by ru@nginx.com - Nginx Development
Привет, Дима! On Wed, Nov 08, 2017 at 08:26:24PM +0300, Dmitry Morozovsky wrote: > Коллеги, > > > что-то мы мальца сломали мозг и явно не видим очевидного. > > Есть ситуация, когда все транзитные HTTP запросы клиента перехватываются и > отправлby ru@nginx.com - Nginx Mailing List - Russian
On Mon, Nov 06, 2017 at 09:35:14PM +0800, 洪志道 wrote: > Hi! > We know that consistent hash upstream improve its selection in the latest > version. > > - if (hp->tries >= points->number) { > - pc->name = hp->rrp.peers->name; > + if (hp->tries > 20) { > ngx_http_upstream_rr_peers_unlock(hp->rrby ru@nginx.com - Nginx Development
On Thu, Nov 02, 2017 at 10:00:34AM -0400, FrenchFry wrote: > I'm new to Nginx and the technology in general. I have spent some time on > nginx.org. The one thing I'm not sure of is if I need to configure my web > server, which is Thin (ruby), with sockets or should TCP be enough. The > reason I ask is because a number of tutorial and blog posts seem to say that > the two serversby ru@nginx.com - Nginx Mailing List - English
On Tue, Oct 31, 2017 at 01:26:45PM -0400, RKGood wrote: > Thank you for your replies. I think we have found the root cause. We have > found below: > > When you are using variables in a proxy_pass directive, nginx will use > runtime resolving except if : > the target server is declared as an IP address There's nothing to resolve if it's an address. > the target serveby ru@nginx.com - Nginx Mailing List - English
details: http://hg.nginx.org/nginx/rev/dc3b3cfd5d23 branches: changeset: 7133:dc3b3cfd5d23 user: Ruslan Ermilov <ru@nginx.com> date: Fri Oct 13 00:32:26 2017 +0300 description: Fixed type of ngx_conf_t.handler_conf. The type should have been changed in c9b243802a17 along with changing ngx_conf_handler_pt. diffstat: src/core/ngx_conf_file.h | 2 +- 1 files changed, 1 insertby ru@nginx.com - Nginx Development
details: http://hg.nginx.org/nginx/rev/882ad033d43c branches: changeset: 7130:882ad033d43c user: Ruslan Ermilov <ru@nginx.com> date: Wed Oct 11 22:04:28 2017 +0300 description: Upstream: fixed $upstream_status when upstream returns 503/504. If proxy_next_upstream includes http_503/http_504, and upstream returns 503/504, $upstream_status converted this to 502 for any values excby ru@nginx.com - Nginx Development
details: http://hg.nginx.org/nginx/rev/f4cf4f970e6e branches: changeset: 7129:f4cf4f970e6e user: Ruslan Ermilov <ru@nginx.com> date: Wed Oct 11 22:04:11 2017 +0300 description: Version bump. diffstat: src/core/nginx.h | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diffs (14 lines): diff -r 3012fcb69db4 -r f4cf4f970e6e src/core/nginx.h --- a/src/core/nginx.h Tuby ru@nginx.com - Nginx Development
details: http://hg.nginx.org/nginx/rev/beeac3302e45 branches: changeset: 7113:beeac3302e45 user: Ruslan Ermilov <ru@nginx.com> date: Mon Sep 25 15:19:24 2017 +0300 description: Fixed the NGX_UNIX_ADDRSTRLEN macro. diffstat: src/core/ngx_inet.h | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diffs (17 lines): diff -r 5a3ab1b5804b -r beeac3302e45 src/core/ngx_inby ru@nginx.com - Nginx Development
On Wed, Sep 27, 2017 at 03:19:43PM +0700, Vadim A. Misbakh-Soloviov wrote: > Прошу прощения за глупый вопрос, но, что-то, в коде у меня сходу не получилось > найти ответ на этот вопрос... > Как NginX относится к повторной загрузке динамического модуля (есby ru@nginx.com - Nginx Mailing List - Russian
details: http://hg.nginx.org/nginx/rev/5a3ab1b5804b branches: changeset: 7112:5a3ab1b5804b user: Ruslan Ermilov <ru@nginx.com> date: Fri Sep 22 22:49:42 2017 +0300 description: Modules compatibility: down flag promoted to a bitmask. It is to be used as a bitmask with various bits set/reset when appropriate. 63b8b157b776 made a similar change to ngx_http_upstream_rr_peer_t.downby ru@nginx.com - Nginx Development
details: http://hg.nginx.org/nginx/rev/6d1f3bb72b07 branches: changeset: 7111:6d1f3bb72b07 user: Ruslan Ermilov <ru@nginx.com> date: Fri Sep 22 18:37:49 2017 +0300 description: Style. diffstat: src/stream/ngx_stream_variables.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diffs (12 lines): diff -r 3b1b81e248bc -r 6d1f3bb72b07 src/stream/ngx_stream_variables.cby ru@nginx.com - Nginx Development