A community driven build of W3 Total Cache. The aim is to continuously incorporate fixes, improvements, and enhancements over the official WordPress release of W3 Total Cache.
We've been chasing a problem on our sites for a few weeks now and we finally pinned it down to a HEAD requests being the first request made after a cache purge. In Redis this creates a key for the page and stores HTML content of two spaces. All subsequent requests to that page will result in a blank page until the cache is purged for that page.
I've noticed on a number of pages describing ideal setups for Total Cache that rejecting HEAD requests is an option, but I don't see it in my install. Has this been removed and does anyone know why? It is still an option to set in the backend, so I set "pgcache.reject.request_head": true, and now our random blank page problem has gone away.
We've been chasing a problem on our sites for a few weeks now and we finally pinned it down to a HEAD requests being the first request made after a cache purge. In Redis this creates a key for the page and stores HTML content of two spaces. All subsequent requests to that page will result in a blank page until the cache is purged for that page.
I've noticed on a number of pages describing ideal setups for Total Cache that rejecting HEAD requests is an option, but I don't see it in my install. Has this been removed and does anyone know why? It is still an option to set in the backend, so I set
"pgcache.reject.request_head": true, and now our random blank page problem has gone away.