Show all posts by user
A portal to and from the mailing list.
Re: connection close on 500, 503, 502. - 8 years ago
ping ?by newnovice - Nginx Mailing List - English
Re: connection close on 500, 503, 502. - 8 years ago
I have this in config: --- error_page 404 =400; error_page 500 502 503 504 =500 @close_conns; location @close_conns { internal; keepalive_timeout 0; } ---- I still see 502's behind returned in '$status' - Why would this happen? I was expecting to see a 500, based on my config. I also see 404's - which should have been transformed to 4by newnovice - Nginx Mailing List - English
Re: connection close on 500, 503, 502. - 8 years ago
Thank you MAXIM - you have been the most responsive & helpful on these forums. GREATLY APPRECIATED.by newnovice - Nginx Mailing List - English
Re: connection close on 500, 503, 502. - 8 years ago
Can i just do this: error_page 404 =400; error_page 502 =500 @close_conns; location @close_conns { internal; keepalive_requests 0; }by newnovice - Nginx Mailing List - English
Re: connection close on 500, 503, 502. - 8 years ago
Can i do something like: (i don't really need a page necessarily - i am purely interested in changing the connection from keep-aline to connection-close) error_page 500 502 503 504 /ServiceUnavailableError.xml; location = /ServiceUnavailableError.xml { root /error_pages/; internal; default_type text/xml; keeby newnovice - Nginx Mailing List - English
connection close on 500, 503, 502. - 8 years ago
Hi There, I want to send a connection_close to the client whenever the HTTP status is any of the 50X codes. How could i accomplish this? Thanks for your response.by newnovice - Nginx Mailing List - English
Re: Trying to Understand Upstream Keepalive - 8 years ago
"isn't enough room in the cache." how big is the upstream keepalive connection-pool cache size?by newnovice - Nginx Mailing List - English
Re: Trying to Understand Upstream Keepalive - 8 years ago
Maxim Dounin Wrote: ------------------------------------------------------- > Hello! > > On Tue, Oct 28, 2014 at 08:01:33PM -0400, newnovice wrote: > > > Maxim, > > > > > http://nginx.org/en/docs/http/ngx_http_upstream_module.html#keepalive > > > > I would like to know what is the keepalive timeout for this > connection pool? > &by newnovice - Nginx Mailing List - English
Re: Trying to Understand Upstream Keepalive - 8 years ago
Maxim, http://nginx.org/en/docs/http/ngx_http_upstream_module.html#keepalive I would like to know what is the keepalive timeout for this connection pool? Is it static? Also i want to understand - if there is a marriage between number of connections nginx gets vs how many it opens to upstream? Thanks!by newnovice - Nginx Mailing List - English
Re: can a map + regex be used to generate variables for YYYY-MM-DD-HH? - 8 years ago
cool so adding the maps & access_log config at http level solved both problems, all logs now goto variable named file. there is no file with --- in the name anymore. thanks!by newnovice - Nginx Mailing List - English
Re: can a map + regex be used to generate variables for YYYY-MM-DD-HH? - 8 years ago
1. variable in logname is what i want: access_log.YYYY-MM-DD-HH I have other log munging daemons looking for this date formatted file in real time (other options i have tried, hard linking files, used named pipes...) 2. (currently i use this method) 'if' - inside server - outside location - works. Only when i get non ssl traffic to 443 port it writes out access_log.---- instead of the usual: 'acby newnovice - Nginx Mailing List - English
Re: can a map + regex be used to generate variables for YYYY-MM-DD-HH? - 8 years ago
Where I am going with this is - I want to write error & access - logs out with the 'YYYY-MM-DD-HH' suffix. So i need these variables. The 'if' statement is not allowed outside the server{} - I am at a loss due to this. Please con you show me some examples of how to set these variables with a map regex? I can have 4 seoerate maps to get it done - doesn't matter.by newnovice - Nginx Mailing List - English
can a map + regex be used to generate variables for YYYY-MM-DD-HH? - 8 years ago
can a map + regex be used to generate variables for YYYY-MM-DD-HH? I cant use 'if' in the location i am trying this. -- I know i can do: if ($time_iso8601 ~ "^(\d{4})-(\d{2})-(\d{2})") { set $year $1; set $month $2; set $day $3; } or with perl regex: if ($time_iso8601 ~ "^(\d{4})-(\d{2})-(\d{2})T(\d{2}):(\d{2}):(\d{2})") { set $year $1;by newnovice - Nginx Mailing List - English
Re: reverse ssl proxy - speed & jitter - 8 years ago
this is for a very fast internal only API driven service and not serving webpages/static files/multimedia...by newnovice - Nginx Mailing List - English
Re: reverse ssl proxy - speed & jitter - 8 years ago
What is the fastest SSL connection setup time that anyone can achieve? and also how do i reduce the jitter/variance.. so what settings should I take out & what shud i have - do you have an example of an optimal config? the logs are turned off to see first if this is even a viable option, i can turn up debug and check stuff if needed.by newnovice - Nginx Mailing List - English
Re: reverse ssl proxy - speed & jitter - 8 years ago
Full Config: #user nobody; # This number should be, at maximum, the number of CPU cores on your system. # (since nginx doesn't benefit from more than one worker per CPU.) worker_processes 5; #give worker processes the priority (nice) you need/wish, it calls setpriority(). worker_priority -10; #decrease number gettimeofday() syscalls. By default gettimeofday() is called after eachby newnovice - Nginx Mailing List - English
reverse ssl proxy - speed & jitter - 8 years ago
I am setting up a nginx reverse ssl proxy - I have a machine I can use with 2 E5-2650 CPU's and lots of RAM. I have nginx-1.6.0 + openssl-1.0.1h installed. I have taken into consideration most optimization suggestions out there and incorporated them. I will attach a copy of my config file. (optimizing first connection experience is good) With my testing just for handshake + connection setup wiby newnovice - Nginx Mailing List - English
Re: Dropped https client connection doesn't drop backend proxy_pass connection - 8 years ago
1. Where can i get a full list of these disabled headers: "By default, nginx does not pass the header fields “Date”, “Server”, “X-Pad”, and “X-Accel-...” from the response of a proxied server to a client. The proxy_hide_header directive sets additional fields that will not be passed. If, on the contrary, the passing of fields needs to be permitted, the proxy_pass_header direby newnovice - Nginx Mailing List - English
Re: Dropped https client connection doesn't drop backend proxy_pass connection - 8 years ago
I tried with: " proxy_pass_header Connection;" -- which should do this according to documentation: "Permits passing otherwise disabled header fields from a proxied server to a client." (from upstream_server to client) But this did not pass thru the Connection header coming from the upstream_server to the client of this proxy. Valentin, can you please eby newnovice - Nginx Mailing List - English
Re: Dropped https client connection doesn't drop backend proxy_pass connection - 8 years ago
Can I proxy_pass on the way back also - and preserve all headers coming from the upstream service?by newnovice - Nginx Mailing List - English
Re: Dropped https client connection doesn't drop backend proxy_pass connection - 8 years ago
Does this also affect a 'Connection Close' header coming from the upstream service - being sent as a connect-keep-alive to the requesting client thru my nginx ssl reverse proxy? (I am trying to setup nginx as an SSL proxy; when the upstream service sends a connection close I want this to be passed on by nginx to the client requesting pages in the fronted.) webbrowser -> 443-nginx-ssl-ofby newnovice - Nginx Mailing List - English
 |
 |
 |
 |
|