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
Hello!
On Wed, Sep 18, 2013 at 02:52:39AM -0400, Claudio wrote:
> 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 suc
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
g all the data, which fails
> eventually:
>
> 2013/09/17 16:17:38 [error] 22873#0: *1 writev() failed (32: Broken pipe)
> while sending request to upstream, client: 192.168.2.8, server: test.int,
> request: "POST /scm/blub?cmd=unbundle HTTP/1.1", upstream:
> "http:
ction
right away:
127.0.0.1 - - [17/Sep/2013:14:17:38 +] "POST /scm/blub?cmd=unbundle
HTTP/1.0" 401 1412
But nginx gratuitously insists on sending all the data, which fails
eventually:
2013/09/17 16:17:38 [error] 22873#0: *1 writev() failed (32: Broken pipe)
while sending request to u
