Issue nginx - ajax

Mon May 26 12:30:30 UTC 2014

Thanks everyone for your help. 

Our issue is not still resolved. 
We are planning to move to apache or squid. 

Thanks & Regards, 
Vishal Mestri 

Thanks & Regards, 
Vishal Mestri 
Module Lead 

2 nd Floor, Dhana Singh Processors Building,Vazir Glass Lane, J B Nagar, Andheri (E). Mumbai – 59. India. 
Mob: +91 99203 87430 | Visit Us : www.cloverinfotech.com 

Stay Connected: 
Description: Description: Description: Description: cid:image006.jpg at 01CE1A91.E5BB71D0Description: Description: Description: Description: cid:image008.jpg at 01CE1A91.E5BB71D0Description: Description: Description: Description: cid:image010.jpg at 01CE1A91.E5BB71D0
P Please consider the environment before printing this e-mail. 
Disclaimer 
The information in Clover Infotech Pvt. Ltd. email and any attachments is confidential and intended solely for the attention and use of the named addressee(s). This information may be subject to legal, professional or other privilege and further distribution of it is strictly prohibited without our authority. If you are not the intended recipient, you may not copy, distribute or disclose its content to any person or entity, use it for any purpose or store or copy the information in any medium. If you have received it in error, please notify the sender immediately and delete the message from your systems. Personal messages and/or opinions in a message are solely those of the author. Clover Infotech Pvt. Ltd. will accept no responsibility for such messages. You are advised to check the message for computer viruses using your own software before opening any attachments. 
----- Original Message -----

From: "Vishal Mestri" <vishal.mestri at cloverinfotech.com> 
To: nginx at nginx.org 
Sent: Friday, May 23, 2014 12:46:46 PM 
Subject: Re: Issue nginx - ajax 

Hi B. R. 

Thanks for your reply and really sorry for the way we conveyed our request. 

We tried to use tcpdump command to trace the issue , but still we are not yet resolved the issue. 

Now we have distributed logging i.e. we are logging differently for port 6401 and we found that request is not forwarded in case of ssl. 

I am attaching here with logs generated. 

error-6401.log_chrom_21may - error log generated when we used chrome 
access.log_chrome_21may - access log generated when we used chrome 

access.log_ie_21may - access log generated when we used ie 
error-6401.log_ie_21may - error log generated when we used ie 

We went through the logs and concluded that , in case of ssl, nginx is not able to forward request to proxy server , when we use IE. 
But we are not able to understand , what is cause of the same. 

If any one can guide us , where exactly we are going wrong. 

Thanks & Regards, 
Vishal Mestri ----- Original Message -----

From: "B.R." <reallfqq-nginx at yahoo.fr> 
To: "Nginx ML" <nginx at nginx.org> 
Sent: Wednesday, May 7, 2014 7:05:02 PM 
Subject: Re: Issue nginx - ajax 

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 
nginx at nginx.org 
http://mailman.nginx.org/mailman/listinfo/nginx 

_______________________________________________ 
nginx mailing list 
nginx at nginx.org 
http://mailman.nginx.org/mailman/listinfo/nginx 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20140526/74037b95/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: access.log_ie_21may
Type: application/octet-stream
Size: 991 bytes
Desc: not available
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20140526/74037b95/attachment-0004.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: access.log_chrome_21may
Type: application/octet-stream
Size: 6742 bytes
Desc: not available
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20140526/74037b95/attachment-0005.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: error-6401.log_ie_21may
Type: application/octet-stream
Size: 19631 bytes
Desc: not available
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20140526/74037b95/attachment-0006.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: error-6401.log_chrom_21may
Type: application/octet-stream
Size: 173467 bytes
Desc: not available
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20140526/74037b95/attachment-0007.obj>