Thanks for the responses guys.
I've tried proxy_store on one config, but now I'm just receiving time-outs
when I block the origin server. No stale cache on error at all.
Here are two separate configs I'm using. The first one is as described
earlier, with caching and stale cache errors working, al
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.
I'd like cache to be browser agnostic.
Any ideas?
It is hard to identify problem
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
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.
Nobody to help? :-(
Regards,
Jan Reges
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hi,
i love Nginx, but i have some specific problem. Nginx cache depends also on
some browser-specific factors.
In one project, we need to work with Nginx as "Static webpage mirror" for
occasional outages or scheduled downtimes of primary server.
99% visitors just browsing this website and only
