We want to pick the backend server to proxy_pass to based on the request method. Saw one example that used limit_except. Another idea would be to use lua. Is there a preferred way to achieve this? Karlby karlseguin - Nginx Mailing List - English
Yes, re-requesting the same image will cause the same error (can't say with 100% certainty that it'll always do it though). sudo hd /mnt/tmp/nginx/cache/5f/85/1b/56cc2e05fb85eb0a806444f1811b855f 00000000 ff d8 ff e0 00 10 4a 46 49 46 00 01 01 00 00 01 |......JFIF......| Naively, there doesn't seem to be any special header bytes? Relevant config is: upstream origin_magick {by karlseguin - Nginx Mailing List - English
Getting OpenSSL to handle md5 didn't change anything (wasn't able to get it to compile with your specific flag, but I figured this was what you had intended?) Here's a sample from the debug log: 2012/09/13 15:15:16 27367#0: *3441 http cache key: "http://origin_magick" 2012/09/13 15:15:16 27367#0: *3441 http cache key: "/uploads/channel/thumbnail/5927/e74e97624ef652bc7a8419cby karlseguin - Nginx Mailing List - English
Hi, Looking for help with a high number of md5 collisions with proxy caching. It's my understanding that we shouldn't be getting any, but we seem to be getting quite a few. -V nginx version: nginx/1.2.3 built by gcc 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) configure arguments: --prefix=/opt/nginx --with-http_stub_status_module --with-pcre=../pcre-8.31 --without-http_access_module --without-httby karlseguin - Nginx Mailing List - English
heh, thanks :) much better!by karlseguin - Nginx Mailing List - English
I was interested in having nginx log 404s to their own file. Essentially, i _hate_ 404s, so I like to parse access logs find and report all 404s. However, as-is, parsing large access logs can be quite inefficient since 404s represent such a small % of the entire file. I was thinking nginx could filter it out at write-time: access_log not_found.log combined buffer=16K 404; Apologies for tby karlseguin - Nginx Mailing List - English