Re: Debugging 504 Gateway Timeout and its actual cause and solution

2016-01-05 Thread Keyur
Thanks Richard & itpp2015 for your response. Further update : There are 2 cases : 1. 504 @ 120 seconds coming with below mentioned error : 2016/01/05 03:50:54 [error] 1070#0: *201650845 upstream timed out (110: Connection timed out) while connecting to upstream, client: 66.249.74.99, server: x.

Re: How to setup Nginx as REALLY static-cache reverse proxy

2016-01-05 Thread Robert Paprocki
Can you show us your config, debug logs, or any info that would help troubleshoot the issue? See https://www.nginx.com/resources/wiki/start/topics/tutorials/debugging/ for help on setting up debug logging. On Tue, Jan 5, 2016 at 9:55 PM, austevo wrote: > I'm having the same issue with cache bein

Re: How to setup Nginx as REALLY static-cache reverse proxy

2016-01-05 Thread austevo
I'm having the same issue with cache being browser dependent. I've tried setting up a crawl job using wget --recursive with Firefox and Chrome headers, but that doesn't seem to trigger server-side caching either. If I browse the site using Firefox, then caching works for Firefox, and Firefox only.