WordPress.org

Ready to get started?Download WordPress

Forums

[resolved] Super Cache shows in Source Code but W3 Total Cache shows in Response Header (6 posts)

  1. jankph
    Member
    Posted 3 years ago #

    I am currently switching between WPSC and W3TC in order to see who works best on husdal.com, but I have an odd problem. When using WPSC my source code says Super Cache, but my response header lists W3 Total Cache:

    Source code

    <!-- Dynamic page generated in xxx seconds. -->
    <!-- Cached page generated by WP-Super-Cache on DATE TIME -->
    <!-- Compression = gzip -->

    Response header

    X-Powered-By W3 Total Cache/0.9.2.2

    I'm using mod rewrite with WPSC if that is any help in sorting this out. Interestingly, before switching to mod rewrite, the response header correctly said php caching, but switching back and forth between php caching and mod rewrite caching now doesn't change anything in the response header now.

    Is this even a problem?

  2. jankph
    Member
    Posted 3 years ago #

    marked as "resolved" due to no answers

  3. Donncha O Caoimh
    Member
    Posted 3 years ago #

    Chances are you're using W3TC though I have no idea why you'd see the Supercache footer message. Sorry.

  4. jankph
    Member
    Posted 3 years ago #

    Donncha,

    Thanks for taking the time to reply. It puzzles me why this would happen.

    I suspect that since I am not making a complete install and uninstall and not deleting the folders, but simply activating or deactivating the installed cache plugins, there could be some mix-up somewhere.

    Having said that, I now switched to Hyper Cache, just for the sake of testing different cache plugins, although I do prefer Super Cache for its Preload function.

  5. kw2
    Member
    Posted 3 years ago #

    W3TC changes your .htaccess-files.
    <IfModule mod_headers.c>
    Header set X-Powered-By "W3 Total Cache/0.9.2.2"
    </IfModule>
    The response header comes from this lines. If you aren't using W3TC anymore, you should clean your .htaccess-files.
    Search for
    # BEGIN W3TC Browser Cache
    ...
    # END W3TC Browser Cache

  6. jankph
    Member
    Posted 3 years ago #

    Thanks kw2. Issue solved.

Topic Closed

This topic has been closed to new replies.

About this Topic