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" <[email protected]> To: [email protected] 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@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 [email protected] http://mailman.nginx.org/mailman/listinfo/nginx
_______________________________________________ nginx mailing list [email protected] http://mailman.nginx.org/mailman/listinfo/nginx
