Title: Cache Tester
Last modified: December 5, 2017

---

# Cache Tester

 *  [wiqi4love](https://wordpress.org/support/users/wiqi4love/)
 * (@wiqi4love)
 * [8 years, 5 months ago](https://wordpress.org/support/topic/cache-tester/)
 * I am facing this error when i test cache. plz help for fix it
 * Fetching [http://www.getpositions.com/](http://www.getpositions.com/) to prime
   cache: FAILED
 * Errors: : cURL error 35: gnutls_handshake() failed: A TLS fatal alert has been
   received.
    Fetching first copy of [http://www.getpositions.com/](http://www.getpositions.com/):
   FAILED
 * Errors: : cURL error 35: gnutls_handshake() failed: A TLS fatal alert has been
   received.
    Fetching second copy of [http://www.getpositions.com/](http://www.getpositions.com/):
   FAILED
 * Errors: : cURL error 35: gnutls_handshake() failed: A TLS fatal alert has been
   received.
    The pages do not match! Timestamps differ or were not found!
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fcache-tester%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 12 replies - 1 through 12 (of 12 total)

 *  Plugin Author [Donncha O Caoimh (a11n)](https://wordpress.org/support/users/donncha/)
 * (@donncha)
 * [8 years, 5 months ago](https://wordpress.org/support/topic/cache-tester/#post-9759630)
 * I think this is an issue with your host and how the software there is compiled.
   I search Google for the CURL error you’re getting and found a few threads about
   people having the same issue. I can’t fix it as it’s not a bug in the plugin.
 *  [hero12](https://wordpress.org/support/users/hero12/)
 * (@hero12)
 * [8 years, 5 months ago](https://wordpress.org/support/topic/cache-tester/#post-9766363)
 * Hello, in my case the pages are OK but
 * “The pages do not match! timestamps differ or were not found!”
    and also, I don’t
   see something like
 *     ```
       <!-- Dynamic page generated in 0.450 seconds. -->
       <!-- Cached page generated by WP-Super-Cache on 2017-12-09 15:13:51 -->
       <!-- super cache -->
       ```
   
 * inside the pages source
 * – Files are correctly written into wp-content/cache
    – I don’t use CDN…
 * I don’t remember that this happened in the past.
 * Please, can you deeply explain why this behavior?
    Thanks
    -  This reply was modified 8 years, 5 months ago by [hero12](https://wordpress.org/support/users/hero12/).
    -  This reply was modified 8 years, 5 months ago by [hero12](https://wordpress.org/support/users/hero12/).
 *  Thread Starter [wiqi4love](https://wordpress.org/support/users/wiqi4love/)
 * (@wiqi4love)
 * [8 years, 5 months ago](https://wordpress.org/support/topic/cache-tester/#post-9766637)
 * [@donncha](https://wordpress.org/support/users/donncha/) thanks for your reply.
   the error was in my ssl certificate, i removed the ssl from my site now its working
   fine.
 *  Thread Starter [wiqi4love](https://wordpress.org/support/users/wiqi4love/)
 * (@wiqi4love)
 * [8 years, 5 months ago](https://wordpress.org/support/topic/cache-tester/#post-9766645)
 * [@hero12](https://wordpress.org/support/users/hero12/) dear can you plz tell 
   me that which cache plugin you r using and are you using cloudflare?
    if u using
   cloudflare so uncheck the html minification and if you are using ani html minification
   plugin try to deactivate it then try.
 *  [hero12](https://wordpress.org/support/users/hero12/)
 * (@hero12)
 * [8 years, 5 months ago](https://wordpress.org/support/topic/cache-tester/#post-9766704)
 * I’m not using cloudflare or minification…
    while it writes files into wp-content/
   cache, there’s no real evidence that is serving pages from the cache. That’s 
   it
 * thanks
 *  [hero12](https://wordpress.org/support/users/hero12/)
 * (@hero12)
 * [8 years, 5 months ago](https://wordpress.org/support/topic/cache-tester/#post-9766733)
 * if it helps, in the FAQ they write about `WPCACHEHOME` but I don’t see that into**
   wp-config.php**
 * is that needed?
 *  [hero12](https://wordpress.org/support/users/hero12/)
 * (@hero12)
 * [8 years, 5 months ago](https://wordpress.org/support/topic/cache-tester/#post-9767069)
 * **FOUND**
 * There’s incompatibility between `mod_pagespeed` AND `WP Super Cache`
    or at least
   with the default mod_pagespeed filters
 * turning off the mod_pagespeed, WP Super Cache works as usual
 * So, please, can you test this configuration and let users know how to use mod_pagespeed
   and WP Super Cache together?
 * Thanks
    -  This reply was modified 8 years, 5 months ago by [hero12](https://wordpress.org/support/users/hero12/).
 *  [hero12](https://wordpress.org/support/users/hero12/)
 * (@hero12)
 * [8 years, 5 months ago](https://wordpress.org/support/topic/cache-tester/#post-9767126)
 * furthermore, I’m not able to isolate the Virtualhost in order to selectively 
   turn off mod_pagespeed
 * I tried
 *     ```
       <IfModule pagespeed_module>
       ModPagespeed off //this one alone, the below alone, even the 2 together
       ModPagespeed unplugged
       </IfModule>
       ```
   
 * nothing to do…
    if mode_pagespeed is **on** in `pagespeed.conf` there’s no way
   to turn it off into the Virtualhost..
 * OR I have no idea how to do it
    -  This reply was modified 8 years, 5 months ago by [hero12](https://wordpress.org/support/users/hero12/).
 *  [hero12](https://wordpress.org/support/users/hero12/)
 * (@hero12)
 * [8 years, 5 months ago](https://wordpress.org/support/topic/cache-tester/#post-9767286)
 * so, found how to disable for the Virtualhost BUT I’m not able to disable it per`
   Directory`
    I wrote on github and waiting for their reply
 * In the meanwhile, to turn it off for the specific virtualhost, you need to write
 *     ```
       <IfModule pagespeed_module>
       ModPagespeed unplugged
       </IfModule>
       ```
   
 * **outside** the Directory rules, otherwise it doesn’t work
    -  This reply was modified 8 years, 5 months ago by [hero12](https://wordpress.org/support/users/hero12/).
 *  Plugin Author [Donncha O Caoimh (a11n)](https://wordpress.org/support/users/donncha/)
 * (@donncha)
 * [8 years, 5 months ago](https://wordpress.org/support/topic/cache-tester/#post-9778808)
 * [@hero12](https://wordpress.org/support/users/hero12/) – thanks for finding that
   out. I’ll add that to the documentation!
 *  Plugin Author [Donncha O Caoimh (a11n)](https://wordpress.org/support/users/donncha/)
 * (@donncha)
 * [8 years, 5 months ago](https://wordpress.org/support/topic/cache-tester/#post-9778825)
 * BTW – I [tried mod_pagespeed in 2010](https://odd.blog/2010/11/08/wp-super-cache-modpagespeed/)
   and ran into problems myself. I haven’t tried it since.
 *  [hero12](https://wordpress.org/support/users/hero12/)
 * (@hero12)
 * [8 years, 5 months ago](https://wordpress.org/support/topic/cache-tester/#post-9780216)
 * I had to
 * `ModPagespeedDisallow "*mydomain.com/mydir/*"`
    into **pagespeed.conf**
 * in order to turn it off per directory
 * they wrote that on the latest versions you could use the `standby` switch (instead
   of `off`) but on CentOS 7 at the moment I don’t get that version

Viewing 12 replies - 1 through 12 (of 12 total)

The topic ‘Cache Tester’ is closed to new replies.

 * ![](https://ps.w.org/wp-super-cache/assets/icon-256x256.png?rev=3506220)
 * [WP Super Cache](https://wordpress.org/plugins/wp-super-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-super-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-super-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-super-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-super-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-super-cache/reviews/)

## Tags

 * [Cache Tester](https://wordpress.org/support/topic-tag/cache-tester/)
 * [cURL error 35](https://wordpress.org/support/topic-tag/curl-error-35/)

 * 12 replies
 * 3 participants
 * Last reply from: [hero12](https://wordpress.org/support/users/hero12/)
 * Last activity: [8 years, 5 months ago](https://wordpress.org/support/topic/cache-tester/#post-9780216)
 * Status: not resolved