Re: Format of messages posted to error_log?

nginx mailing list -- nginx@nginx.org To unsubscribe send an email to nginx-le...@nginx.org -- Cheers, Oleg A. Mamontov ___ nginx mailing list -- nginx@nginx.org To unsubscribe send an email to nginx-le...@nginx.org

Upstream get stuck in disabled state for websocket load balancing

My current nginx configuration looks like: worker_processes 1; error_log /dev/stdout debug; events { worker_connections 1024; } http { upstream back { server backend1 max_fails=1 fail_timeout=10; server backend2 max_fails=1 fail_timeout=10; } server { listen 80; locat

Re: Empty file "off" under /usr/local/nginx/

osted at Nginx Forum: https://forum.nginx.org/read.php?2,287577,287577#msg-287577 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx -- Cheers, Oleg A. Mamontov mailto: o...@mamontov.net skype: lonerr11 cell:

Re: Regex in proxy_hide_header

On Wed, May 02, 2018 at 01:14:58PM +, bmrf wrote: Oleg A. Mamontov Wrote: --- On Wed, May 02, 2018 at 09:34:04AM +, bmrf wrote: >Hi list, > >I was trying to unset/delete a header using proxy_hide_header. The problem >is tha

Re: Regex in proxy_hide_header

nd of the header name to specify a pattern." Thanks a lot! -- Cheers, Oleg A. Mamontov mailto: o...@mamontov.net skype: lonerr11 cell: +7 (903) 798-1352 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

NGINX is hiring

Hello, NGINX is seeking a Russian-speaking technical support engineer: https://www.nginx.com/jobs/enterprise-support-engineer-russian-speaking/ Please feel free to send your questions and CV directly to me: lon...@nginx.com. Thank you. -- Cheers, Oleg A. Mamontov

Re: access log request without query string

ustomized 404 error page /404.html, all those requests are logged as > /404.html instead of original requests uri. > > Thanks! > Frank -- Cheers, Oleg A. Mamontov mailto: o...@mamontov.net skype: lonerr11 cell: +7 (903) 798-1352 _

Re: forced 404 without a location display ?

> = location /paths/to/ { if ( !-f /etc/nginx/_flags/is_running ) { rewrite ^ /is_running last; } } location = /is_running { internal; return 404 'nothing\n'; }

Re: Nginx fastcgi_next_upstream off doesn't work

Yes, you are absolutely right. Thanks again! ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: Nginx fastcgi_intercept_errors

Many thanks, works like a charm. The reason is Wrong location settings. On Fri, Nov 29, 2013 at 5:02 PM, Maxim Dounin wrote: > Hello! > > On Fri, Nov 29, 2013 at 04:59:56PM +0400, Maxim Dounin wrote: > > > Hello! > > > > On Fri, Nov 29, 2013 at 03:36:18PM

Re: Nginx fastcgi_intercept_errors

custon log format where I captured 504 response. It is set only for root location where I captured unexpected response code. Thanks, OK On Fri, Nov 29, 2013 at 4:59 PM, Maxim Dounin wrote: > Hello! > > On Fri, Nov 29, 2013 at 03:36:18PM +0400, Oleg V. Khrustov wrote: > > >

Nginx fastcgi_next_upstream off doesn't work

nginx/1.5.4 location / { ... fastcgi_pass bg; fastcgi_next_upstream off; ... } upstream bg { server unix:/tmp/dsp.1.sock; server unix:/tmp/dsp.2.sock; server unix:/tmp/dsp.3.sock; server unix:/tmp/dsp.4.sock; server unix:/tmp/dsp.5.sock; server unix:/tmp/

Nginx fastcgi_intercept_errors

nginx/1.5.4 doesnt intercept fastcgi errors. location / { fastcgi_pass bg; error_page 500 502 503 504 408 404 =204 /204.htm; fastcgi_intercept_errors on; . } However in root location access log we still see 91.192.148.232 - - [29/Nov/2013:13:39:20 +0400]