You are reading WP-Cache 2.1 revisited: Have x-gzip and gzip compression share same cache slot. You can leave a comment or trackback this post.
Posted on April 10th, 2007 by Reiner.
Categories: English, Computers.
While working on the 304 not modified case that causes excessive traffic for RSS feeds, I encountered a mild weakness within the compression code, that causes both gzip and x-gzip variants of a particular page to use separate cache slots (i.e. two separate files). That’s quite redundant, as x-gzip is just a lagacy term to invoke gzip processing and both x-gzip and gzip produce identical contents.
Now, only a single cache slot is being used for both and the value of the Content-Encoding header (either gzip or x-gzip) is no longer cached, but instead derived from the current request being served.
There’s no code here, as it will be included within the 304 not modified version.
0 comments.
Comments can contain some xhtml. Names and emails are required (emails aren't displayed), url's are optional.