Found it! The solution was in a a mailing list item from 2012. You have to
turn proxy buffering on in order for the proxy cache to work. I'm caching
like a champ now.
There probably ought to be a warning about that someplace, or it should be
in the docs someplace.
On Mon, Feb 29, 2016 at 2:03 PM
The catch-all entry works and don't conflict with the = /. That solves my
second problem, thank you!
On Mon, Feb 29, 2016 at 3:32 PM, Wandenberg Peixoto
wrote:
> The location = / is a exactly match.
> To execute a "catch all" returning a 404 you can do a
>
> location / {
> return 404;
> }
> O
The location = / is a exactly match.
To execute a "catch all" returning a 404 you can do a
location / {
return 404;
}
On Feb 29, 2016 16:15, "Payam Chychi" wrote:
> Look at your proxy cache path... (proxy_cache_path /var/www/test_cache)
> Are you sure the path exists and had proper perms/owner
Yes, it does exist:
stat /var/www/test_cache
File: `/var/www/test_cache'
Size: 4096Blocks: 8 IO Block: 4096 directory
Device: 802h/2050d Inode: 22195081Links: 2
Access: (0700/drwx--) Uid: ( 497/ nginx) Gid: (0/root)
Access: 2016-02-29 15:14:19
Look at your proxy cache path... (proxy_cache_path /var/www/test_cache)Are you
sure the path exists and had proper perms/ownership?
Payam
On Feb 29, 2016, 11:03 AM -0800, CJ Ess, wrote:
> Hello! I'm testing out a new configuration and there are two issues with the
> proxy cacheing feature I'm
Hello! I'm testing out a new configuration and there are two issues with
the proxy cacheing feature I'm getting stuck on.
1) Everything is a cache miss, and I'm not sure why:
My cache config (anonymized):
...
proxy_cache_path /var/www/test_cache levels=2:2 keys_zone=TEST:32m
inactive=365d max_si
