WordPress.org

Ready to get started?Download WordPress

Forums

WP Super Cache
Different Web Browsers Served Different Cache Copies? (2 posts)

  1. ispreview
    Member
    Posted 1 year ago #

    I've noted with the latest official release of your plugin that different web browsers appear to be served with different cache files. I haven't tested this on other computers to see if it's more than a browser related problem and occurs per-computer.

    The issue I have with this is obviously that the system is over-caching the same page multiple times, which mitigates the advantages of caching, when it should only be doing this once and updating according to the timed settings or whether I add new posts etc.

    For example it's 15:52 when I check the front page of my website and I noticed that the page views reported by different browsers is not in sync. After looking at the bottom of the source code I also see that different cache times and related files for the same page are also being called.

    Under IE9 the front page cache line reads:

    <!-- Dynamic page generated in 0.634 seconds. -->
    <!-- Cached page generated by WP-Super-Cache on 2012-11-30 15:44:26 -->

    Under Firefox v16 the front page cache line reads:

    <!-- Dynamic page generated in 0.639 seconds. -->
    <!-- Cached page generated by WP-Super-Cache on 2012-11-30 15:39:24 -->
    <!-- super cache -->

    Under Chrome the front page cache line reads:

    <!-- Dynamic page generated in 0.642 seconds. -->
    <!-- Cached page generated by WP-Super-Cache on 2012-11-30 15:44:30 -->

    They use to all be loading from the same cached file and time. I consider this to be quite a critical bug or is it something I've done?

    I've conducted various tests and even from a fresh wipe it creates a new file for each web browser, which makes no sense to me.

    http://wordpress.org/extend/plugins/wp-super-cache/

  2. thinkingman
    Member
    Posted 1 year ago #

    Actually, many plugins I’ve come across have a poor code practice of generating different HTML depending on the User Agent string (this was pretty common [even for me] back in the days before you could rely on CSS for most degradation issues). Thus, the tendency will be for different cache files to be created for different browsers--always--unless you hack your wp-config to change the UA, which is a very disrecommended course of action...

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags