Got this message after changing the cache path? Could not find a solution after googling it. Any help? 15154#15154: cache "my_zone" uses the "/dev/shm/nginx" cache path while previously it used the "/tmp/nginx" cache path nginx -V nginx version: nginx/1.11.3 built with OpenSSL 1.0.2h 3 May 2016 TLS SNI support enabled configure arguments: --with-cc-opt='by shiz - Nginx Mailing List - English
For reference, that snippet seem to have done the job. I'm not redirecting them, I trash them though. if ($args ~* "^param\%"){ access_log off; return 410; }by shiz - Nginx Mailing List - English
If you're from the apache world, nginx configuration if often counter-intuitive. Does the following help? # To find location matching a given request, nginx first checks locations defined # using the prefix strings (prefix locations). Among them, the location with the # longest matching prefix is selected and remembered. # Then regular expressions are checked, in the order of their appeby shiz - Nginx Mailing List - English
Strange, cannot find 1.11.x Maybe you mean 1.10.0? root@NC-PH-0657-10:/usr/local/src/nginx# wget http://nginx.org/download/nginx-1.11.0.tar.gz --2016-04-29 10:53:26-- http://nginx.org/download/nginx-1.11.0.tar.gz Resolving nginx.org (nginx.org)... 206.251.255.63, 95.211.80.227, 2001:1af8:4060:a004:21::e3 Connecting to nginx.org (nginx.org)|206.251.255.63|:80... connected. HTTP requestby shiz - Nginx Mailing List - English
Hi, Sometimes, bots are notorious for doing that, arguments are over urlencoded. If someone knew a way to rewrite them back to their normal state, that would be awesome. e.g. Normal URL: www.site.com/file.php?param=blahblah URLs that bots try sometimes (often in fact - don't know where they get those strings BTW): www.site.com/file.php?param%253Dblahblah www.site.com/file.php?pby shiz - Nginx Mailing List - English
Yes it's resolved. I've change the cache path yesterday and a few minutes ago, I noticed that error message: "2016/03/19 12:31:02 8984#8984: cache "my_zone" uses the "/tmp/nginx/dev" cache path while previously it used the "/tmp/nginx" cache path" It seems it was enough to prevent the cache from running. Interesting. BTW, do you see anything usby shiz - Nginx Mailing List - English
Been playing with this for 2 days. proxy_pass is working correctly but the proxy_cache_path remains empty whatever I make. Here's the source I use for tests: root@NC-PH-0657-10:/etc/nginx/snippets# curl -X GET -I http://www.kuriyama-truck.com/images/parts/13375/thumbnail_0/1_1.jpg HTTP/1.1 200 OK Date: Sat, 19 Mar 2016 18:15:16 GMT Server: Apache/2.4.16 (Amazon) PHP/5.6.17 Last-Modifiby shiz - Nginx Mailing List - English