Re: access log request without query string

Maybe lua-nginx-module is more convenient :) On 20 April 2017 at 08:08:46, Frank Liu (gfrank...@gmail.com) wrote: Hi, What's the best way to login the original request uri ($request_uri) without query string? I tried $uri but it seems to be normalized and if I have customized 404 error page

access log request without query string

Hi, What's the best way to login the original request uri ($request_uri) without query string? I tried $uri but it seems to be normalized and if I have customized 404 error page /404.html, all those requests are logged as /404.html instead of original requests uri. Thanks! Frank

Re: Logging all requests onNginx

this might be helpful - http://stackoverflow.com/questions/12315832/how-to-fix-nginx-throws-400-bad-request-headers-on-any-header-testing-tools/17289826#comment16555393_12315832 On Wed, Apr 19, 2017 at 7:53 PM, Jeff Dyke wrote: > untested, but if you set error_log to the

Re: Logging all requests onNginx

untested, but if you set error_log to the correct level, it should log there as it likely received a > 300 response from the backends. I don't think you want these in your access logs, but i am suprised you don't get some sort of non < 400 response in those logs. But it's been a long day On

Re: Logging all requests onNginx

Will it not be logged as a timeout either in access or error/log ? On 20 April 2017 at 03:46, aT wrote: > HI , > > Is there a way to log all incoming requests on Nginx . > > Regardless of them being served or not . > > For example, In case of surge of crawler hits , if the

Re: crash in ngx_add_timer

Thanks Ben, That worked! I wonder why these data-structures where not initialized earlier? On Tue, Apr 18, 2017 at 7:23 PM, 734819342 <734819...@qq.com> wrote: > Hi, > > > U should not call ngx_add_timer there, cause ngx_event_timer_rbtree > is initialized in [init process]. > > >

Logging all requests onNginx

HI , Is there a way to log all incoming requests on Nginx . Regardless of them being served or not . For example, In case of surge of crawler hits , if the upstream backend cannot perform and requests hang , nginx will not log any such failed request . How can we log them to have more detail

Re: GPG Key ( nginx_signing.key) file does not contain the key to verify the tar file

Hello! On Wed, Apr 19, 2017 at 12:18:07PM -0400, Kumudini Ponnuthurai wrote: > Not able to verify the latest source of mainline and stable versions of > NGINX with gpg key ( http://nginx.org/keys/nginx_signing.key ). I am using > Gpg4win Kleopatra. I uploaded this nginx_signing.key file, then

GPG Key ( nginx_signing.key) file does not contain the key to verify the tar file

Not able to verify the latest source of mainline and stable versions of NGINX with gpg key ( http://nginx.org/keys/nginx_signing.key ). I am using Gpg4win Kleopatra. I uploaded this nginx_signing.key file, then changed the owner trust under certificates. Then verified the source (tar file and the

Re: nginx development guide

Hello, On 13/02/2017 12:38, Vladimir Homutov wrote: > Hello all! > > We are glad to share with first results of our ongoing efforts to create > documentation for nginx developers: the development guide document [1]. > > The guide is not yet 100% complete and more parts to follow. > > Of

Re: nginx development guide

Привет. On 13/02/2017 12:39, Vladimir Homutov wrote: > Добрый день! > > Мы рады поделиться с вами первыми результатами наших усилий по созданию > документации для разработчиков nginx: руководством разработчика [1] (en) > > Конечно, руководство не полностью закончено, надеемся, будут и другие

Re: upstream - behavior on pool exhaustion

On Wed, Apr 19, 2017 at 10:51 AM, Ruslan Ermilov wrote: > And what about the next request when all of servers are either "down" > or "unavailable"? > To me, all the unavailable servers have been 'tried', ie their state has been checked, as the docs

Re: [PATCH] Contrib: vim syntax, support block region

Hello! On Wed, Apr 19, 2017 at 05:52:36PM +0800, OOO wrote: > Hi Dounin > > I have looked into your POC. > I use this approach in yajs.vim too. > The major problem of this approach is: It creates (sort of) redundant > syntax group. > For the listen directive: > > > syn keyword

[njs] Fixed parsing ISO 8601 format in Date.parse().

details: http://hg.nginx.org/njs/rev/96fda9957427 branches: changeset: 340:96fda9957427 user: Andrey Zelenkov date: Wed Apr 19 17:48:56 2017 +0300 description: Fixed parsing ISO 8601 format in Date.parse(). Fixed parsing in case milliseconds are not specified.

Re: [PATCH] Contrib: vim syntax, support block region

Hi Dounin I have looked into your POC. I use this approach in yajs.vim too. The major problem of this approach is: It creates (sort of) redundant syntax group. For the listen directive: > syn keyword ngxDirectiveImportantListen listen > \ nextgroup=@ngxListenParams skipwhite skipempty > syn

Re: upstream - behavior on pool exhaustion

On Tue, Apr 18, 2017 at 02:39:27PM +0200, B.R. via nginx wrote: > 'down' should not translate into any kind of attempt, so nothing should > really appear for the servers in that static state. > For 'unavailable' servers, for the most part the content of the variables > should be the same. > >