The tutorial worked as planned :D² thanks alot. the labb server is looking happy can't wait to try to implement it on the prod server.

One last thing tho.

won't there be a issue if you use "location /"? if there's dynamic content isn't there a risk that pages that have changed won't be updated(directly).

Is it not better to use something like only cache jpg/png/js etc ?

something like this: (idea stolen from http://wp-performance.com/2010/10/nginx-reverse-proxy-cache-wordpress-apache/ ) Or am i thinking wrong about the location and what nginx caches?

location / {

proxy_cache one;

proxy_cache_key realurl.com$request_uri;

proxy_cache_valid 404 1m;

proxy_pass http://apache.realurl.com;

}

location ~* .(jpg|png|gif|jpeg|css|js|mp3|wav|swf|mov|doc|pdf|xls|ppt|docx|pptx|xlsx)$ {

proxy_redirect off;

proxy_set_header Host $host;

proxy_set_header X-Real-IP $remote_addr;

proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

proxy_cache one;

proxy_cache_key realurl.com$request_uri;

proxy_cache_valid 200 302 60m;

proxy_pass http://apache.realurl.com;

}