UDP load balancing - 1 new socket for each incoming packet?

2016-08-31 Thread Gwenole Gendrot
Hi, I've been using nginx 1.11.3 to test the UDP load balancing feature, using a "basic" configuration. The functionality is working out of the box, but a new socket will be created by the proxy for each packet sent from a client (to the same connection). This leads to resource exhaustion und

Re: Nginx multiple upstream map conditions

2016-08-31 Thread c0nw0nk
c0nw0nk Wrote: --- > Francis Daly Wrote: > --- > > On Wed, Aug 31, 2016 at 01:30:30PM -0400, c0nw0nk wrote: > > > > Hi there, > > > > > Thanks works a treat is it possible or allowed to do the

Re: Nginx multiple upstream map conditions

2016-08-31 Thread c0nw0nk
Francis Daly Wrote: --- > On Wed, Aug 31, 2016 at 01:30:30PM -0400, c0nw0nk wrote: > > Hi there, > > > Thanks works a treat is it possible or allowed to do the following > in a > > nginx upstream map ? and if so how i can't figure it out. > > I

Re: Nginx multiple upstream map conditions

2016-08-31 Thread Francis Daly
On Wed, Aug 31, 2016 at 01:30:30PM -0400, c0nw0nk wrote: Hi there, > Thanks works a treat is it possible or allowed to do the following in a > nginx upstream map ? and if so how i can't figure it out. I think it is logically impossible. > I cache with the following key. > fastcgi_cache_key > "$

looks nice

2016-08-31 Thread gavidmogarrr
Hey friend, I've recently came accross that amazing stuff, it looks nice I think, ytake a look All best, gavidmogarrr ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listin

Re: Nginx multiple upstream map conditions

2016-08-31 Thread c0nw0nk
Valentin V. Bartenev Wrote: --- > On Tuesday 30 August 2016 14:25:28 c0nw0nk wrote: > > So this is a fun one. > > > > As allot of people probably already know you can't use "IF" on > upstream > > values since if conditions are executed before any

Re: Nginx multiple upstream map conditions

2016-08-31 Thread c0nw0nk
Thanks works a treat is it possible or allowed to do the following in a nginx upstream map ? and if so how i can't figure it out. I cache with the following key. fastcgi_cache_key "$session_id_value$scheme$host$request_uri$request_method"; if the upstream_cookie_logged_in value is not equal to

Re: Nginx multiple upstream map conditions

2016-08-31 Thread Valentin V. Bartenev
On Tuesday 30 August 2016 14:25:28 c0nw0nk wrote: > So this is a fun one. > > As allot of people probably already know you can't use "IF" on upstream > values since if conditions are executed before any "$upstream_" conditions. > > But with a map directive it might just be possible to combine 2 u

Re: log status actually not real status

2016-08-31 Thread Valentin V. Bartenev
On Wednesday 31 August 2016 04:30:51 crasyangel wrote: > Nginx would log status to 200 after response header had sent when upstream > prematurely closed connection > I think nginx should log status to 502, even though client recv 200 [..] Why do you think so? wbr, Valentin V. Bartenev

Re: NGINX to support websocket client on the same port

2016-08-31 Thread Valentin V. Bartenev
On Wednesday 31 August 2016 01:21:13 jebina wrote: > A quick question, Does Nginx support websocket client. > > I have a webserver that uses NGINX and i use a websocket server for which > NGINX acts as proxy. In the same port , can i use websocket client to > initiate a connection with the externa

RE: Log the headers sent by nginx to upstream server

2016-08-31 Thread Maxim Ozerov
"Log format can contain common variables, and variables that exist only at the time of a log write" So, other options I do not see, except ngx_http_log_module But, .. interesting thing is what it means to be overwritten?) Nginx, some adjustments in request headers, receives from the client: - N

log status actually not real status

2016-08-31 Thread crasyangel
Nginx would log status to 200 after response header had sent when upstream prematurely closed connection I think nginx should log status to 502, even though client recv 200 static u_char * ngx_http_log_status(ngx_http_request_t *r, u_char *buf, ngx_http_log_op_t *op) { ngx_uint_t status;

Log the headers sent by nginx to upstream server

2016-08-31 Thread Sushma
My client sends a request to nginx with a http header set. This header is overwritten by nginx before passing along the reqest to the downstream server. I want to log the header after modification by nginx. I understand that we can log the header sent by client using "$http_". Is there some embedd