Wrong mimetype when served from nginx

2015-07-09 Thread Cédric Jeanneret
Hello, I have a small issue with my nginx (1.2.1) configuration: some files are served as "application/octet-stream" while they are detected as "text/plain" by "mimetype " command. File names are just "1", "2", and so on. Is there a way to enforce mimetype for those files? I thought about somet

Do not log "directory index of /foo/bar/ is forbidden"

2015-07-09 Thread basti
Hello, I have found "conditional logging" in http://nginx.org/en/docs/http/ngx_http_log_module.html It seems that it only works on status codes. Is there a way to disable logging for something like: 2015/07/09 11:02:30 [error] 24928#0: *97983 directory index of "/foo/bar/" is forbidden, client:

Re: *_cache_revalidate directives

2015-07-09 Thread Roman Arutyunyan
Hello, > On 09 Jul 2015, at 10:59, Alt wrote: > > Hello Roman, > > Thanks for the explanation. > At which moment this revalidation is executed? When there's a new client > request or is it done automatically when a cache entry is about to expire? When there’s a client request. Nginx does not d

Re: *_cache_revalidate directives

2015-07-09 Thread Alt
Hello Roman, Thanks for the explanation. At which moment this revalidation is executed? When there's a new client request or is it done automatically when a cache entry is about to expire? The nginx's cache manager is deleting expiring cache file, so I'm not sure to understand how it all works. B

Re: *_cache_revalidate directives

2015-07-09 Thread Roman Arutyunyan
Hello, > On 09 Jul 2015, at 04:43, Alt wrote: > > Hello, > > From the documentation, I don't understand how the fastcgi_cache_revalidate > (or scgi_cache_revalidate or proxy_cache_revalidate or > uwsgi_cache_revalidate) works. > Please, can someone explain what nginx does when cache is enabled