Never mind - a new proxy target was misconfigured. Doh!by useopenid - Nginx Mailing List - English
Additional information: I caught it in the act, and something about this trigger and the setup is causing nginx to loop - the client ip address is actually right and nginx is proxying the request to itself as fast as it can. Restarting nginx stops the loop. This is version 0.7.65. I tried upgrading to 1.7.4 recently but the syslog support doesn't seem to work for mail and I haven't gotten a chaby useopenid - Nginx Mailing List - English
We have a cluster of 4 nginx proxies behind a piranha load balancer setup. This morning we suffered a DOS attack, however the "client" address appears to have only gotten logged correctly the first time, the rest have the virtual ip address targeted as the "client", and it's unclear how or why that would happen. The setup is in "direct return" mode... Thanks for anby useopenid - Nginx Mailing List - English
Thanks! I setup stunnel in the interim, but this will be more efficient.by useopenid - Nginx Mailing List - English
I'm getting errors when I try to get the diff, is it still available? Thanks...by useopenid - Nginx Mailing List - English
I am looking at proxying to google as well, and thus need SSL on the backside (and would like it on general principles for other cases as well), however it does not appear that nginx supports this. I would expect this to be the default if an incoming connection is using ssl, or, at the very least, specified in the protocol parameter in the server {} block (e.g. pop3s, imaps, smtps or smtp-starttlby useopenid - Nginx Mailing List - English