I already tried this

Here's the config

fastcgi_cache_path /data/nginx/cache levels=1:2 keys_zone=one:10m inactive=7d max_size=200m; fastcgi_temp_path /data/nginx/temp;

location @joomla { fastcgi_pass 127.0.0.1:9000; fastcgi_param SCRIPT_FILENAME /home/kompastv/web/index.php; fastcgi_cache one; fastcgi_cache_key 127.0.0.1:9000$request_uri; fastcgi_cache_valid 200 1h;

/data/nginx/cache and /data/nginx/temp is still empty

root 28119 0.0 0.0 13940 496 ? Ss 15:41 0:00 nginx: master process /etc/nginxnew/sbin/nginx -c /etc/nginx/nginx.conf nginx 28120 1.3 0.2 17328 4408 ? R 15:41 0:01 nginx: worker process nginx 28122 1.6 0.2 17384 4540 ? S 15:41 0:01 nginx: worker process nginx 28123 0.0 0.0 14096 800 ? S 15:41 0:00 nginx: cache manager process

is there somethink i've missed?

-----Original Message----- From: owne...@sysoev.ru [mailto:owne...@sysoev.ru] On Behalf

Sysoev Sent: 21 April 2009 15:32 To: ngi...@sysoev.ru Subject: Re: which one is better?

On Tue, Apr 21, 2009 at 03:10:31PM +0700, Glen Lumanau wrote:

Yes, just s/proxy/fastcgi/.

The single difference is that fastcgi cache requires

fastcgi_cache_key localhost:9000$request_uri;

while proxy_cache may use default one, similar to this:

proxy_cache_key $scheme$proxy_host$uri$is_args$args;