ru@nginx.com Wrote: [...] > From the log it follows that client closed a connection before > the entire request body was sent. From the config it follows > that http://nginx.org/r/proxy_request_buffering is "on" (which > is the default setting). It means that no upstream server was > ever contacted, so it's perfectly okay that $upstream_addr is > undefinedby ywarnier - Nginx Mailing List - English
And the usual debug information I just found on https://www.nginx.com/resources/wiki/start/topics/tutorials/debugging/ that I should provide (very sorry for doing that in 3 parts, won't happen again): #### nginx -V nginx version: nginx/1.10.0 (Ubuntu) built with OpenSSL 1.0.2g 1 Mar 2016 TLS SNI support enabled configure arguments: --with-cc-opt='-g -O2 -fPIE -fstack-protector-strong -Wforby ywarnier - Nginx Mailing List - English
Sometimes writing your thought helps... Apparently something wasn't reporting correctly so far, but using the debug level, I finally end up getting some information. I should mention that the word that seems to provoke this issue is ' del ' (with two spaces around it). If those 3 letters are included in another word, nothing weird happens. When the word is there on its own, though, this is myby ywarnier - Nginx Mailing List - English
Hi guys, I have a problem with some of the requests sent to my Nginx load balancer, which reports (in the access_log configured to show $upstream_addr) that $upstream_addr is equal to "-", but only in a weird case where the post contains the word "del". I'm using Nginx 1.10.0 packaged in Ubuntu 16.04.4, in a development cluster of VMs with Nginx serving as load balancer tby ywarnier - Nginx Mailing List - English
Just an update: as of today, even Debian provides libssl1.0.0:1.0.1e-2+deb7u16 which still generates these error logs, so it looks like the only way is still to fallback to libssl1.0.0:1.0.1e-2+deb7u12.by ywarnier - Nginx Mailing List - English