Re: Encrypting TLS client certificates`

2016-10-25 Thread Rainer Duffner
> Am 26.10.2016 um 01:20 schrieb WGH : > > When nginx requests a client certificate with ssl_verify_client option, > and client complies, the latter sends its certificate in plain text. > > Although it's just a public part of the certificate, one can consider it > a kind of information disclosur

round robin rule

2016-10-25 Thread Frank Liu
If I configure one "upstream" with 2 servers and use the default round robin, will the traffic be balanced based on the upstream or the virtual servers. e.g.: if I configure 2 virtual host "server" blocks, both proxy_pass the same upstream, will the requests to each virtual host be balanced individ

Encrypting TLS client certificates`

2016-10-25 Thread WGH
When nginx requests a client certificate with ssl_verify_client option, and client complies, the latter sends its certificate in plain text. Although it's just a public part of the certificate, one can consider it a kind of information disclosure, since user name, email, organization, etc. is tran

Re: Does http pipeline prevent nginx from graceful shutdown active connections?

2016-10-25 Thread Valentin V. Bartenev
On Tuesday 25 October 2016 16:30:38 Jeremy Gates wrote: > Hi, all > > I found a recent code commit of Nginx fixed one issue that prevent nginx > from graceful shutdown active connections for HTTP/2: > > http://hg.nginx.org/nginx/rev/5e95b9fb33b7 > > Just for curiosity, I was wondering if this is

Does http pipeline prevent nginx from graceful shutdown active connections?

2016-10-25 Thread Jeremy Gates
Hi, all I found a recent code commit of Nginx fixed one issue that prevent nginx from graceful shutdown active connections for HTTP/2: http://hg.nginx.org/nginx/rev/5e95b9fb33b7 Just for curiosity, I was wondering if this is a problem for pipelined HTTP requests. Thanks, Jeremy

nginx 502

2016-10-25 Thread Answer
log_format access '$remote_addr - $remote_user [$time_local] "$request" $http_host $status $body_bytes_sent "$http_referer" "$http_x_forwarded_for" "$upstream_addr" "$upstream_status" $upstream_cache_status "$upstream_http_content_type" "$upstream_response_time" > $request_time "$http_user_age

Re: Bug? Chown of all default *_temp_path directories at startup?

2016-10-25 Thread Maxim Dounin
Hello! On Tue, Oct 25, 2016 at 04:45:34PM +0200, Daniel Aubry wrote: [...] > I do have several nginx inscances on one Server, they all run as a > different users. > > There is one main nginx instance which runs as the user www-data. > > *_temp_path is set to a different location for all ngin

Bug? Chown of all default *_temp_path directories at startup?

2016-10-25 Thread Daniel Aubry
Hi all I'm using nginx-full 1.10.2-1~dotdeb+8.1 from dotdeb.org on Debian. nginx -V nginx version: nginx/1.10.2 built with OpenSSL 1.0.1t 3 May 2016 TLS SNI support enabled configure arguments: --with-cc-opt='-g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2' -

How to delay requests from once unauthorized IP address

2016-10-25 Thread hide
Hello! My Nginx does fastcgi_pass to some CGI application. The CGI application can return HTTP status code 401. I want Nginx to return this status code to the user and prevent the next access of the user to the CGI application for 5 seconds. For example, the user accessed the CGI application thro