<Module mod_rewrite.c>
 RewriteEngine On
 RewriteCond %{HTTP_USER_AGENT} !^CoralWebPrx
 RewriteCond %{QUERY_STRING} !(^|&amp;)coral-no-serve$
 RewriteCond %{HTTP_COOKIE} heavyloaduser=true [OR]
 RewriteCond %{HTTP_REFERER} slashdot\.org [NC]
 RewriteCond %{HTTP_REFERER} digg\.com [NC,OR]
 RewriteRule ^(.*)$ http://%{HTTP_HOST}.nyud.net%{REQUEST_URI}  [R,L,CO=heavyloaduser:true:%{HTTP_HOST}]
</IfModule>

Which will rewrite all traffic from digg to coralcdn (http://www.coralcdn.org/). It is possible to keep the comments dynamic and uncached by adapting these rules slightly, adding in something like:

RewriteCond %{REQUEST_URI}      !^/comment\.php

I am unsure of how wordpress handles comments, so this may/may not work.

Hope this helps

I’m not sure about the .htaccess however, is there any risk if it is owned by the same user as Wordpress (user in the unix-sense)? I can see that there is a problem with chmod 777, but chown shouldn’t make a difference I think.

Personally id redirect to google cache (if generated) or remove all aspects of page except content and advert and redirect to that.

Wordpress uses large amount of server requests, even when using wpcache such as javascript files and images.

Adam @ zend.is-hacked.com