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 please double-check that the behaviour you describe > appears when using nginxby sdnetwork - Nginx Mailing List - English
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 38111#38111: *4098505 upstream prematurely closed connection while reading response header from upstream, client: x.x.x.x, server: x.x.com, request: "GET /query?uid=b85cc8a4-b9cd-4093-aea5-95c0ea1391a6_428 can you confirm that is my node server that close theby sdnetwork - Nginx Mailing List - English
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 access.log x.x.x.x - - [09/Jul/2017:09:18:33 +0200] "GET /query?uid=b85cc8a4-b9cd-4093-aea5-95c0eaby sdnetwork - Nginx Mailing List - English