Thanks, that seems to work. But I still don't quite understand how. I did use both directives with the same variable. Now when I set "proxy_cache_bypass 0;", it seems to correctly cache images and serve that cache. I'd imagine that unconditional 0 in that directive would cause nothing being served from cache ever (as that variable is considered first). By the way, my Nginx version is 1.3by burn - Nginx Mailing List - English
Right. The problem is that there were images as well. And now when I swapped values, it seems that nothing at all is cached.by burn - Nginx Mailing List - English
with "proxy_no_cache $no_proxy;", there are css files in cache again.by burn - Nginx Mailing List - English
but I'm not using upstream directive. Do you mean that it's only possible to upstream instead of direct proxy_pass? I tried that. I still see non-image files in cache.by burn - Nginx Mailing List - English
can you elaborate on how to implement it? For me, it seems to cache html as well (I'm checking saved files). Here's what I come up with: nginx.conf user nginx; worker_processes 8; worker_rlimit_nofile 100000; error_log /var/log/nginx/error.log; pid /var/run/nginx.pid; events { worker_connections 1024; use epoll; } http { include /etc/nginx/mime.types;by burn - Nginx Mailing List - English
Like the title says, can I cache images (or whatever) by mime type, not extension? The only relevant info I found is at http://stackoverflow.com/questions/6212361/nginx-cache-file-by-mime-type However, the suggested config is not valid, because proxy directive cannot be used inside if.by burn - Nginx Mailing List - English
Hello. I'm trying to install nginx 1.0.11 on Centos 5.7 x86_64. Server runs cpanel, so this version and compliling from source are mandatory. Nginxcp.com provides cpanel plugin, and I'm using its installation script. But it's failing. I was able to track it down to this: ./configure: error: can not define uint64_t I've found a solution here at mailing lists that suggests adding CFLAGS="&quoby burn - Other discussion
well, then please consider this a feature request. Having two separate packages for our server farm is not too convenient.by burn - Nginx Mailing List - English
If you install nginx compiled with aio support on non-aio enabled kernel, it doesn't work: 2011/04/15 11:46:25 18942#0: io_setup() failed (1: Operation not permitted) 2011/04/15 11:46:25 18938#0: worker process 18942 exited with fatal code 2 and can not be respawn All workers die, only master process remains, requests aren't servedby burn - Nginx Mailing List - English
this would be a highly appreciated feature. Please add syslog support to nginx.by burn - Nginx Mailing List - English