• Sometimes I see this header:

    HTTP/1.1 200 OK
    X-Powered-By: PHP/7.0.20
    Content-Type: text/html; charset=UTF-8
    Vary: Accept-Encoding, Cookie
    Cache-Control: max-age=3, must-revalidate
    WP-Super-Cache: Served supercache file from PHP
    Last-Modified: Fri, 30 Jun 2017 01:39:30 GMT
    Content-Length: 13090
    Date: Fri, 30 Jun 2017 01:41:27 GMT
    Accept-Ranges: bytes
    Server: LiteSpeed
    Connection: close

    Sometimes it switches to this one:

    HTTP/1.1 200 OK
    X-Powered-By: PHP/7.0.20
    Vary: Cookie
    Content-Type: text/html; charset=UTF-8
    Link: <https://oneoffmakery.net.au/wp-json/&gt;; rel=”https://api.w.org/&#8221;
    Link: <https://oneoffmakery.net.au/&gt;; rel=shortlink
    Date: Fri, 30 Jun 2017 01:38:08 GMT
    Accept-Ranges: bytes
    Server: LiteSpeed
    Connection: close

    It seems to switch back to the first (correct, WP Cache is working, right?) one when I log in to the admin panel and use the Test Cache feature. It seems to switch to the second (wrong) one after some time.

    Any ideas what could be happening?

Viewing 1 replies (of 1 total)
  • Thread Starter gbell12

    (@gbell12)

    What I think was happening was that since I was using curl -I, which only does a HEAD request, WP Super Cache wasn’t creating the cache entry, nor serving it. Visiting the page with a browser would create the entry.

    I’m guessing something was expiring, so the 2nd header is what’s served when there’s no entry.

Viewing 1 replies (of 1 total)
  • The topic ‘WP Super cache not always serving’ is closed to new replies.