That is a dummy IP. Now, seeing is believing -- I gave it another try and it actually gave me the response similar to the screenshot. Not sure why but it is very sporadic. I believe that, if cache file doesn't exist response is still 404. Of course, the cache file exists, therefore question is - why so sporadic. Wouldn't be helpful to return a message "cache file does not exists" iby skynet - Nginx Mailing List - English
74.65.58.194 - - [15/Mar/2010:00:35:29 -0400] "GET /purge/ HTTP/1.0" 404 1656 "-" "Wget/1.11.4 Red Hat modified" upstream_response_time - msec 1268627729.628 request_time 0.000 Expires: - Cache-Control: - upstream_cache_status - Question: what am I supposed to see/get after a successful purge? Thanks for all your help Piotr but I don't want to waste your timeby skynet - Nginx Mailing List - English
Public URL is http://www.mysite.com/test-2/2220 To request purge I try (on local server): wget www.mysite.com/purge/test-2/2220 or directly from browser (from one of the IPs in allow): www.mysite.com/purge/test-2/2220 log_format combinedx '$remote_addr - $remote_user [$time_local] ' '"$request" $status $body_bytes_sent ' '"$http_refeby skynet - Nginx Mailing List - English
Here's the config: location ~ ^/purge(/.*)$ { allow 127.0.0.1; allow 192.168.0.0/16; allow 72.12.74.93; deny all; proxy_cache_purge staticfilecache "$scheme://$host$1"; }by skynet - Nginx Mailing List - English
> Just to make sure: are you requesting purges from > localhost (127.0.0.1)? No, why would I, nginx is listening to external IP. > At this time it only logs successful purges at > http debug level and failures > to delete files from hard disk at critical level. how do I see this log? it will give me a clue into what the proxy_cache_purge is doing > > > Itby skynet - Nginx Mailing List - English
It seems that I keep getting upstream_cache_status UPDATING Does that mean the purging is scheduled somehow?by skynet - Nginx Mailing List - English
Piotr - is there any way to get proxy_cache_purge to log its activity? I am not sure it is even working, although I do not get any error message when restarting NGINX.by skynet - Nginx Mailing List - English
My "purge" URL for the home-page (http://www.mysite.com/) is http://www.mysite.com/purge/ I get a 404 and nothing gets purged. Same thing if I do it for a URL of this form: http://www.mysite.com/test-2/2220 http://www.mysite.com/purge/test-2/2220 won't do anything, just getting a 404. GET /test-2/2220 upstream_cache_status HIT GET /purge/test-2/2220 upsby skynet - Nginx Mailing List - English
Can somebody confirm that proxy_cache_purge is working with nginx/0.8.34. I have this config and cannot get it to delete anything from the cache, I just get a 404: location / { proxy_pass http://127.0.0.1:8000; proxy_cache tmpcache; proxy_cache_key "$scheme://$host$request_uri"; } location ~ /purge(/.*) { allow 127.0.0.1; deny all; proxy_cache_purge tmpcachby skynet - Nginx Mailing List - English