We don't explicitly set the proxy_cache_key - we use the default value provided by NGINX. From the docs at http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_cache_key I understood that the query string is part of the cache key - I'm reaching out for help because it doesn't work as I'd expect.by 0liver - Nginx Mailing List - English
We've recently started delivering image urls with query strings for cropping, like http://images-camping.info/CampsiteImages/116914_Large.jpg?width=453&height=302&mode=crop We've also successfully been using the NGINX cache for our images *before* adding the query strings. Unfortunately, with the query strings added, caching does not work anymore and all requests to above URL areby 0liver - Nginx Mailing List - English
Thanks a lot, Jader. Your hint saved me hours of additional headache after our site was almost unusable due to NGINX throwing tens of thousands of "24: Too many open files" errors. I chose to set *worker_rlimit_nofile* to 65536 = 2^16 for peace of mind :-) It's important to note, that the *worker_connections* count needs to be adapted as well, so that connections now won't be droppby 0liver - Nginx Mailing List - English
I'm facing the same problem here, but I found much lower settings on our machine (a VPS running Ubuntu 12.04): # the hard limit of open files www-data@215247:~$ ulimit -Hn 4096 # the soft limit of open files www-data@215247:~$ ulimit -Sn 1024 # maximum number of file descriptors enforced on a kernel level # for more info see: http://serverfault.com/q/122679/88043 root@215247:~# cat /proby 0liver - Nginx Mailing List - English
Hi there, just a few moments ago I posted an answer to a question in the "How to..." forum, and I was looking really hard to find a way to emphasize the most important parts of my answer and format the nginx configuration code for better readability. Unfortunately, I didn't find any way to do that. Here's what I tried: - using simple html markup like <b>this should be bold<by 0liver - Site Suggestions
Hello Doctau, I'm relatively new to nginx as well, but I think I can propose a solution to your problem. You could use a regular expression (flagged by ~) in your location path to match both /supervision and /nagios: location ~ ^(/supervision|/nagios) { ---> // your config here } I haven't tested this, but I hope my regex fu hasn't failed me. The ^ character says that the match shby 0liver - How to...
I understand it works like this: By chance, the ip_hash module hashed your IP to be forwarded to the first tomcat. Now, since "tomcat 1" is down, you're being forwarded to "tomcat 2". But since nginx tries to check if "tomcat 1" is back up and your IP matched to it, it tries to connect to "tomcat 1" again on your next request. Then it registers that it'sby 0liver - How to...