I can confirm from my end that the page gets redis page cached only after second visit of the page
I will try a face installation and then I will confirm again
Fresh installation, sorry about the typo
Hi there! You might be requesting the page with different cache keys, so you’re both being served a different cache copy, hence the miss on the first request from the header check tool.
If you turn on the debug option in the plugin (see the configuration code) you’ll see the actual cache keys being used and compare the two. Things the key depends on: request variables, cookies, authentication requests and any explicitly defined unique values.
It seems to be working after a Fresh install. But I don’t understand the cache key concept
I use Redis Object Cache as well
Cache keys are just a way of addressing a specific cached page in the database. For example “post:1” could be an unhashed cache key that points to the dump of a rendered HTML page with a post ID of 1. “post:1:mobile” could be the mobile version of post ID 1. So a unique name for a single piece of cached data. Cache keys are built from the request data, then hashed using md5 to put a constraint on space.
If you turn on debugging, as stated above, you’ll be able to see which specific unhashed cache key the current response was saved under.
Please turn on debugging Redis_Page_Cache::$debug = true and paste some of the X-Pj headers.
Hope this makes sense.
