Hello,
(Short version: what could cause nginx to try to resolve a name used as the
upstream backend configured name? Long version follows in the body of the
message).
I have a weird problem, which might be something simple I am missing, I
searched the archives and read the documentation twice and
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
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
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
