Disk: Enhanced and query strings Suggestion…

First, Disk Enhanced mode is quite clever and very quick and works with Apache and even Ngnix which is slightly quicker.

But you can’t use query strings, obviously because you don’t want some page that uses a query string to get cached because then the next user that loaded that page would see the results from the original cached page which could be based on a different query string.

Looking at the way the Disk Enhanced files are stored they usually are in a directory structure but the file is stored as _index.html_gzip and _index.html. So why not md5 the query string and prepend it to _index.html file?

Then in Apache you can use RewriteMap that points to an file that creates the md5 hash when there is a query sting. Then if the file exists just serve it out directly regular html or _gzip depending on the requesting browser. These RewriteMap prg files are very quick because they are started when Apache is started and they just run a continuous loop waiting for Apache to pass some data so it can return the md5.

The slight drawback is that only people that have access to the httpd.conf vituralhost would be able to get the RewriteMap file to get loaded. But the rewrite could be done in .htaccess file with a return of something like “not_found” when the map was not loaded. So the not_found would just not ever work with queries, just like page_enhanced does not currently work with queries.

Craig

http://wordpress.org/plugins/w3-total-cache/