Re: Slow read attack in HTTP/2

2016-08-19 Thread Валентин Бартенев
On Friday 19 August 2016 18:07:46 Sharan J wrote: > Hi, > > Thanks for the response. > > Would like to know what happens in the following scenario, > > Client sets its initial congestion window size to be very small and > requests for a large data. It updates the window size everytime when it >

Re: why will nginx's map directive eat all ram?

2013-08-02 Thread Валентин Бартенев
On Friday 02 August 2013 16:30:35 Payne Chu wrote: > recently I try to use map directive to make my nginx.conf DRY. like below > > `map $pid $public_root { default public; }` > > and in one of server directive I put below > > `root $public_root;` > > I try to `ab` test with retrieve a static ht

Re: Possible bug http2 module

2016-02-06 Thread Валентин Бартенев
On Saturday 06 February 2016 12:13:52 Jim Ohlstein wrote: > Hello, > > I am running a WordPress multisite install and recently turned off http2 > on the domain in order to use a third party module which evidently > doesn't play nicely with http2 (echo module). In testing I noticed that > the site

Re: Possible bug http2 module

2016-02-06 Thread Валентин Бартенев
On Saturday 06 February 2016 12:44:08 Jim Ohlstein wrote: > On 2/6/16 12:22 PM, Валентин Бартенев wrote: > > On Saturday 06 February 2016 12:13:52 Jim Ohlstein wrote: > >> Hello, > >> > >> I am running a WordPress multisite install and recently turned off http

Re: SPDY + HTTP/2

2016-02-09 Thread Валентин Бартенев
On Tuesday 09 February 2016 05:06:39 mongia.ramandeep wrote: > I was able to patch nginx-1.9.10 which supports both SPDY + HTTP2. I don't > intend to use both of them simultaneously on the same interface. > > My question: Is there a reason why this is not done? It gives me an option > to choose be

Re: access_log in stream context

2016-02-19 Thread Валентин Бартенев
On Friday 19 February 2016 12:34:12 cubicdaiya wrote: > Hello. > > I have been trying the stream module. > But the way to record an access log (e.g. IP address) from a client is not > found. > > > Is access_log in stream context support planed in the future? > [..] There's no need in access_lo

Re: enable reuseport then only one worker is working?

2016-02-28 Thread Валентин Бартенев
On Sunday 28 February 2016 08:52:12 meteor8488 wrote: > Hi All, > > I just upgrade Nginx from 1.8 o 1.9 on my FreeBSD box. [..] > Did I miss anything in the configuration? or for a busy server, it's better > to use accept_mutex instead of reuseport? > [..] In FreeBSD the SO_REUSEPORT option has

Re: TCP Connection

2016-03-04 Thread Валентин Бартенев
On Friday 04 March 2016 19:12:56 Giulio Loffreda wrote: > Still having no luck. > No log is generated. > > TCP connection has any relation to web socket support configuration ? > > this is my site config. > > server { > listen 80; > server_name myhost.com; > access_log /v

Re: TCP Connection

2016-03-04 Thread Валентин Бартенев
On Friday 04 March 2016 23:25:27 Giulio Loffreda wrote: > Here is my nginx.conf and site config. > After calling tcp connection and getting http 400, no log is generated. > > I’m following > > Thanks > > server { > listen 80; > server_name apidvc.sparkgo.cc; > access_log

Re: convert $msec to sec

2016-04-03 Thread Валентин Бартенев
On Sunday 03 April 2016 11:31:08 Anoop Alias wrote: > I need to log the seconds since epoch (without the millisecond resolution) > in the access_log file > > is there is a way to convert the $msec to seconds or drop the exponential > part of the time . Probably using the map function?. > It's ea

Re: convert $msec to sec

2016-04-03 Thread Валентин Бартенев
On Sunday 03 April 2016 20:40:33 Anoop Alias wrote: > Thanks Valentin. That works. > > Can you explain > This is simple named subpattern: http://www.pcre.org/original/doc/html/pcrepattern.html#SEC16 used in the map directive: http://nginx.org/r/map wbr, Valentin V. Bartenev

Re: 1.9.14 - Issues with disabled request buffering and HTTP/2

2016-04-11 Thread Валентин Бартенев
On Monday 11 April 2016 05:19:17 n.dom wrote: > Hello, > > we have an issue with the newest nginx version 1.9.14. I am not sure if this > is a possible bug or a configuration problem. > > We use nginx with disabled request buffering (proxy_request_buffering off) > > We are currently using nginx

Re: upstream member liveness

2016-04-11 Thread Валентин Бартенев
On Monday 11 April 2016 07:01:01 drookie wrote: > What is the scope of the upstream member liveness: is it per upstream group, > or per vhost ? > It's per upstream group. > If the question is unclear, consider I have 3 nginx - one balancer and two > backends, and the following config part on th

Re: gzip working for 443 but not 80 in same listener?

2016-04-12 Thread Валентин Бартенев
On Tuesday 12 April 2016 16:48:27 lfisher wrote: > I added port 80 in my listener. > # HTTPS server > server { >listen 80; >listen 443 ssl; > > Gzip still works on 443, but css/js are not getting gzipped in port 80. > > My nginx.conf has > gzip on; > gzip_vary on; > g

Re: upstream member liveness

2016-04-13 Thread Валентин Бартенев
On Wednesday 13 April 2016 00:47:14 drookie wrote: > Is there someone besides Captain Evidence who knows the answer ? This is > actually the problem of the modern internet: half of the decent questions is > flooded out by people, who not only think they know the answer, but are > arrogant enough to

Re: load balancing % available

2016-04-13 Thread Валентин Бартенев
On Wednesday 13 April 2016 12:21:52 B.R. wrote: > As per the docs, I do not see a mean of doing what you wish directly in an > upstream block. > That cut-off might be a feature request you could post on their bug tracker. > > In the meanwhile, you might parse data about servers from an upstream gr

Re: unknown directive "proxy_ssl"

2016-04-14 Thread Валентин Бартенев
On Thursday 14 April 2016 00:46:05 Jorge Romero wrote: > Hi, > > I’m trying to configure Nginx 1.9.7 as a proxy server. This proxy server > won’t serve as SSL termination for HTTPS requests, for which the proxy_ssl > directive sounds perfect. > > http://nginx.org/en/docs/stream/ngx_stream_proxy

Re: nginx returns 503 when it gets 403 from haproxy

2016-04-15 Thread Валентин Бартенев
On Thursday 14 April 2016 22:45:36 CJ Ess wrote: > In my environment I have Nginx terminating connections, then sending them > to an HAProxy upstream. We've noticed that whenever HAProxy emts a 403 > error (Forbidden, in response to our ACL rules), NGINX reports a 503 result > (service unavailable)