> > I request all Nginx master/experts to help me. > That looks like an odd way to *ask* for help. If you wanna *request* help, consider getting paid support. But even doing that, that is rude...
What the error says is that the '*backend* closed connection prematurely'... You should look into it when processing the crashing request. Based on the logs, for that request, nginx received different headers depending on using either IE or Chrome: *IE* "GET /Stream.html?s=0&d=%22168.189.9.09%22&p=450&t=1399381478365 HTTP/1.0 Host: 168.189.9.09:6400 Connection: close Accept: text/html, application/xhtml+xml, */* Referer: http://168.189.9.09:443/Login.do;jsessionid=23A0D509FE7135EC4AB85B757E8BC62E Accept-Language: en-US User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko Accept-Encoding: gzip, deflate DNT: 1 " *Chrome* "GET /Stream.html?s=0&d=%22168.189.9.09%22&p=0&t=1399381806838 HTTP/1.0 Host: 168.189.9.09:6400 Connection: close Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.131 Safari/537.36 Referer: http://168.189.9.09:443/Login.do Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8,id;q=0.6 Cookie: JSESSIONID=4965E0227151FBACCBF61DB65CDF9F9A " Cookie? :o) Look into your application in the backend which does not answer when some conditions, the problem does not seem to come from nginx which forwards requests to yourf backend. --- *B. R.*
_______________________________________________ nginx mailing list [email protected] http://mailman.nginx.org/mailman/listinfo/nginx
