Hello,
>
> The error indicate that your backend server closed the connection.
> That's more less all nginx knows, so if you want to find out why
> your backend did this - consider looking into the backend.
>
i found the problem, there is by default a 180s timeout on my backend.
> Could you
Hello!
On Thu, Jul 13, 2017 at 02:18:34PM +0200, Arnaud Le-roy wrote:
> a little question about the error :
>
> >> 2017/07/09 09:18:31 [error] 38111#38111: *4098505 upstream prematurely
> >> closed connection while reading response header from upstream, client:
> >> x.x.x.x, server: x.x.com, r
Thank you very much for you explanation, it is now clear for me !
a little question about the error :
>> 2017/07/09 09:18:31 [error] 38111#38111: *4098505 upstream prematurely
>> closed connection while reading response header from upstream, client:
>> x.x.x.x, server: x.x.com, request: "GET
>
Hello!
On Sun, Jul 09, 2017 at 11:26:47PM +0200, Arnaud Le-roy wrote:
> i encountered a strange behaviour with nginx, my backend seems
> to receive twice the same request from nginx proxy, to be sure
> that it's not the client that send two request i have had an
> uuid params to each request.
Hello,
i encountered a strange behaviour with nginx, my backend seems to receive twice
the same request from nginx proxy, to be sure that it's not the client that
send two request i have had an uuid params to each request.
when the problem occurs in nginx log i found one request in success in
