Issue nginx - ajax

Wed May 7 10:38:17 UTC 2014

Hi All, 

today I have removed ssl configuration and tested with only http settings. 

i.e. we received request on http port 443 and forwarded it to 80 using nginx. 
Further, we also received request on http port 6401 and forwarded it to 6400 using nginx. 

Application worked successfully on chrome, but we faced issue on IE again. 

Please find attached logs for IE as well Chrome generated at Nginx. 

I guess this issue is related to some http header not being passed which might be caused issue. 

Note: Communication on 443 to 80 is working fine. But when we use ajax to call 6401 port, we face issue. 

Please let me know if any one need any more details. 

I request all Nginx master/experts to help me. 

Regards, 
Vishal 

----- Original Message -----

From: "Vishal Mestri" <vishal.mestri at cloverinfotech.com> 
To: nginx at nginx.org, steve at greengecko.co.nz 
Sent: Tuesday, May 6, 2014 5:48:21 PM 
Subject: Re: Issue nginx - ajax 

Hi All, 

I have enabled debug option on the nginx now. 

After that I have connected using chrome , its working fine. 
But I am facing issue on IE. 

I have attached along with two different error logs with debug enabled. 
ssl_1_chrome.txt -> log generated when we connected using chrome successfully. 
ssl_1_ie.txt -> log generated when we connected using ie , but not sucess. 

I hope this is maximum level of inputs I can provide. 
Requesting all nginx experts to provide help. 

Thanks in advance. 

Regards, 
Vishal 

----- Original Message -----

From: "Vishal Mestri" <vishal.mestri at cloverinfotech.com> 
To: nginx at nginx.org, steve at greengecko.co.nz 
Sent: Tuesday, May 6, 2014 8:53:56 AM 
Subject: Re: Issue nginx 

Hi All, 

please go through below email and help me resolve issue as i am new to nginx. 

Regards, 
Vishal 

----- Original Message -----

From: "Vishal Mestri" <vishal.mestri at cloverinfotech.com> 
To: nginx at nginx.org, steve at greengecko.co.nz 
Sent: Monday, May 5, 2014 1:26:15 PM 
Subject: Re: Issue nginx 

Hi Steve, 

We are getting below error in log file 

2014/05/05 07:50:29 [error] 8800#0: *21 upstream prematurely closed connection while reading upstream, client: 14.97.74.48, server: 168.189.9.09, request: "GET /Stream.html?s=0&d=%22168.189.9.09%22&p=0&t=1399276681085 HTTP/1.1", upstream: "http://168.189.9.09:6400/Stream.html?s=0&d=%22168.189.9.09%22&p=0&t=1399276681085", host: "168.189.9.09:6401", referrer: "https://168.189.9.09/Login.do" 

----- Original Message -----

From: "Vishal Mestri" <vishal.mestri at cloverinfotech.com> 
To: nginx at nginx.org, steve at greengecko.co.nz 
Sent: Monday, May 5, 2014 12:47:04 PM 
Subject: Re: Issue nginx 

Thanks for your immediate reply steve. 

But I just want to know whether we can log request and response headers in nginx, for more debugging. 

As far as code is concerned , we are using , it is running if we don't use nginx. 
Only when we use proxy pass, it is failing. 

One important point , we are using ajax on port 6400 and on port 6401 we have done ssl enablement. 

Can you please help me to debug this issue. 

Thanks in advance. 

Regards, 
Vishal 

----- Original Message -----

From: "Steve Holdoway" <steve at greengecko.co.nz> 
To: nginx at nginx.org 
Sent: Monday, May 5, 2014 12:45:27 PM 
Subject: Re: Issue nginx 

Hi, 

On Mon, 2014-05-05 at 12:21 +0530, Vishal Mestri wrote: 
> I am facing issue with nginx. 
> 
> 
> Its working on Chrome. But not on IE10 and firefox. 
> 
> 
> I am using proxy pass, please find attached nginx.conf file attached 
> along with. 
> 
> 
> 
> 
> OUTPUT OF command: 
> [root at erttrepsg63 ~]# /usr/sbin/nginx -V 
> nginx version: nginx/1.6.0 
> built by gcc 4.4.7 20120313 (Red Hat 4.4.7-3) (GCC) 
> TLS SNI support enabled 
> configure arguments: --prefix=/etc/nginx --sbin-path=/usr/sbin/nginx 
> --conf-path=/etc/nginx/nginx.conf 
> --error-log-path=/var/log/nginx/error.log 
> --http-log-path=/var/log/nginx/access.log 
> --pid-path=/var/run/nginx.pid --lock-path=/var/run/nginx.lock 
> --http-client-body-temp-path=/var/cache/nginx/client_temp 
> --http-proxy-temp-path=/var/cache/nginx/proxy_temp 
> --http-fastcgi-temp-path=/var/cache/nginx/fastcgi_temp 
> --http-uwsgi-temp-path=/var/cache/nginx/uwsgi_temp 
> --http-scgi-temp-path=/var/cache/nginx/scgi_temp --user=nginx 
> --group=nginx --with-http_ssl_module --with-http_realip_module 
> --with-http_addition_module --with-http_sub_module 
> --with-http_dav_module --with-http_flv_module --with-http_mp4_module 
> --with-http_gunzip_module --with-http_gzip_static_module 
> --with-http_random_index_module --with-http_secure_link_module 
> --with-http_stub_status_module --with-http_auth_request_module 
> --with-mail --with-mail_ssl_module --with-file-aio --with-ipv6 
> --with-http_spdy_module --with-cc-opt='-O2 -g -pipe 
> -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector 
> --param=ssp-buffer-size=4 -m64 -mtune=generic' 
> 
> 
> 
> Thanks & Regards, 
> 
> Vishal Mestri 

I'd've said that the code being delivered to each browser is exactly the same ( ok, not necessarily true but you have to force it to be different ), so would look at the accuracy of the html / javascript on the page as a first step. 

Try a basic hello world page and see if that is displayed ok... 

Steve 
-- 
Steve Holdoway BSc(Hons) MIITP 
http://www.greengecko.co.nz 
Linkedin: http://www.linkedin.com/in/steveholdoway 
Skype: sholdowa 

_______________________________________________ 
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/20140507/a3d5fa75/attachment-0001.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: http_1_ie.txt
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20140507/a3d5fa75/attachment-0002.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: http_1_chrome.txt
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20140507/a3d5fa75/attachment-0003.txt>