Hello Maxim, thanks a lot for your explanation. I've (kind off) solved the problem for now. I was testing with another proxy in between nginx and the Jetty server to see whether that would behave differently. I just used Twitter's finagle, which is based on Netty and got a few error messages like this: 18.09.2013 11:59:58 com.twitter.finagle.builder.SourceTrackingMonitor handle FATAL: Aby Claudio - Nginx Mailing List - English
Hi Maxim. Maxim Dounin Wrote: ------------------------------------------------------- > As long as a connection is closed before nginx is able to get a > response - it looks like a problem in your backend. Normally such > connections need lingering close to make sure a client has a chance > to read a response. Thanks for your prompt response! I read an illustrative deby Claudio - Nginx Mailing List - English
Hi. I've set up nginx as a proxy for a jetty service. Works nicely, most of the time, except ... when issuing a (somewhat) larger POST request to some entity which is protected by HTTP Basic access authentication. The web app responds with a 401 immediately, probably closing the connection right away: 127.0.0.1 - - [17/Sep/2013:14:17:38 +0000] "POST /scm/blub?cmd=unbundle HTTP/1by Claudio - Nginx Mailing List - English