Re: access log request without query string

2017-04-19 Thread Zhang Chao
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 /40

access log request without query string

2017-04-19 Thread Frank Liu
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

2017-04-19 Thread Jeff Dyke
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 correct level, it should

Re: Logging all requests onNginx

2017-04-19 Thread Jeff Dyke
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 W

Re: Logging all requests onNginx

2017-04-19 Thread Alex Samad
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 upstream backend > ca

Logging all requests onNginx

2017-04-19 Thread aT
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

2017-04-19 Thread Maxim Dounin
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 cha

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

2017-04-19 Thread Kumudini Ponnuthurai
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: upstream - behavior on pool exhaustion

2017-04-19 Thread B.R. via nginx
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: upstream - behavior on pool exhaustion

2017-04-19 Thread Ruslan Ermilov
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. > > Star