Opened 13 years ago
Last modified 4 years ago
#157 closed defect
inactive= parameter is ignored in proxy_cache_path directive — at Initial Version
| Reported by: | Tom Kostin | Owned by: | somebody |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | nginx-core | Version: | 1.2.x |
| Keywords: | proxy_cache_path max_size | Cc: | |
| uname -a: | Linux sfw4-p 2.6.18-238.12.1.el5 #1 SMP Tue May 31 13:22:04 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux | ||
| nginx -V: |
nginx version: nginx/1.2.0
built by gcc 4.1.2 20080704 (Red Hat 4.1.2-50) TLS SNI support disabled configure arguments: --prefix=/usr --conf-path=/etc/nginx/nginx.conf --error-log-path=/var/log/nginx/error.log --http-log-path=/var/log/nginx/access.log --pid-path=/var/run/nginx.pid --http-client-body-temp-path=/var/lib/nginx/tmp/client_body/ --http-fastcgi-temp-path=/var/lib/nginx/tmp/fastcgi/ --http-proxy-temp-path=/var/lib/nginx/tmp/proxy/ --with-http_ssl_module --with-http_stub_status_module --with-http_geoip_module |
||
Description
No matter what I write in inactive= parameter in proxy_cache_path directive - it is always
resolved to 10 minutes .
I tried different formats :
inactive=14d
inactive=2w
inactive=336h
but the result is always the same : 10 minutes .
Checked both by counting files in cache and manually doing ls -ltr in cache dir .
This bug exists in 1.0.15 too .
This bug does NOT exist in 0.8.55 ( the version we had to roll back to ) .
relevant lines :
proxy_cache_path /ssd/two levels=1:2:2 keys_zone=static:2000m inactive=14d max_size=120000m;
proxy_temp_path /ssd/temp;
in some server :
location /images {
expires 5d ;
proxy_pass http://static-local.domain:80;
proxy_cache_valid 2w;
proxy_cache static;
proxy_cache_use_stale error timeout invalid_header updating http_500 http_502 http_503 http_504;
}
