The documentation for the proxy_cache_path directive of the NginxHttpProxyModule states that the "Key and filename in cache is md5 of proxied URL". Here is an example: a user requests: http://nginx.foo.com/bar.html nginx has the proxy_pass directive: proxy_pass http://apache.foo.com/ the cached filename will be the md5 of: http://apache.foo.com/bar.html Thisby schmoove - Nginx Mailing List - English
OK, I have given up on this. I am now parsing my request URI directly in my web-app instead of relying on nginx rewrite. I have received some helpful information from some nice guys in freenode #nginx, suggesting to parse the $request_uri var in nginx which might not have been canonicalized, but I haven't tried that.by schmoove - How to...
Removing the quotes results in an error: 'directive "rewrite" is not terminated by ";"'. I have got the rewrite to work (sort of) with quotes by now. With some further testing I have encountered the following behavior: It seems as if the problem is with the quantifiers {0,3} and {0,6}. The rewrite works when both quantifiers match 1+ times and fail when matched 0 times. I amby schmoove - How to...
I have a rewrite rule that works with Apache's mod_rewrite but not with nginx rewrite. I find this peculiar, since I thought both use a PCRE lib. Perhaps someone can help me getting this PCRE expression to work with with nginx rewrite: rewrite "^/({2,4})\/([0-9]{0,3})\/([0-9a-zA-Z]{0,6})\/(*)\/(.*)\.png$" /test.bar; here is an example url that does not get rewritten via this rule:by schmoove - How to...