Hello! How correct is the assumption that nginx will always treat Encoded URLs in requests same as un-encoded unless processing of urls is manually overridden by custom rules to intercept requests and change the cache key? Note: nginx is configured as reverse proxy Bottom line is, I have a client who needs to have urls like: %2Fpath%2to%2Ffile.ext treated differently than: /path/by idabic - Nginx Mailing List - English
Thanks for your answer, highly appreciated!by idabic - Nginx Mailing List - English
I have bounced around quite a lot through forums and documentation to demistique whether the OPTIONS request method is honoured/allowed by nginx when it's configured as reverse proxy cache system or not. I used a test box with nginx 1.4.6 with "proxy_cache_methods GET OPTIONS;" to test certain use case for a client but, reloading nginx returned obvious exception that: "iby idabic - Nginx Mailing List - English