strange behavior for cache manager

Hi, we are current running nginx version 1.7.6, we use nginx primarily as a reverse proxy on linux. we have encountered a strange behavior for nginx cache manager, everything is fine after restart nginx, the cache manage periodically spawn new process to check the meta data and honor the max cache

Re: Ipad autodiscovery

I might have read it wrong but it seems that you could create fake files the device is looking for or just return a 200 for such requests. Posted at Nginx Forum: http://forum.nginx.org/read.php?2,256151,256165#msg-256165 ___ nginx mailing list nginx@ng

Re: Ipad autodiscovery

Thanks for the pointer. I took a look at the solution. From what I gather though, that user used his solution for all clients. My problem that I am trying to figure out is that the Android Phones work just fine. I guess I was just trying to see if anyone could help me figure why only the later mode

[ANN] Windows nginx 1.7.10.1 Gryphon

19:14 17-1-2015 nginx 1.7.10.1 Gryphon Based on nginx 1.7.10 (15-1-2015, last changeset 5964:0a198a517eaf) with; + reverted changeset 5962:727177743c3c (causing segfaults) + set-misc-nginx-module v0.27 (upgraded 14-1-2015) + HttpSubsModule v0.6.4 (upgraded 14-1-2015) + lua-nginx-module v0.9.13 (up

Nginx auth users

Hello i am slowly migrating from apache to Nginx So far everything is running smoothly and i have to say from all the benchmark tests Nginx has improved performance by 60% that is incredible and i havent even drived into performance tuning. Anyway we have numerous websites that require a list of

Re: Limiting gzip_static to two directories.

According to the location directive documentation, nginx will match one location block only. nginx will first match the longest prefix location to your request. If that longest prefix is the one you provided, then regular expression