You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 23, 2019. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.The text was updated successfully, but these errors were encountered: