[Plugin: WP Super Cache] Cache Working On A Per User Basis? (6 posts)

  1. orbalon
    Posted 7 years ago #

    I was testing my site in multiple browsers and noticed the query count and timing I have in the footer. On the same page in one browser (as an anonymous user) it stays the same if I refresh the page. But if I open a different browser and go to that same page it creates a new cache file which is then served to that user over and over again upon refresh. Shouldn't all users see the same cached page?

    Note I'm using half-on mode because of an mfunc command. I tried disabling that code, removed the mfunc etc and my results were the same as mentioned above.

    Am I missing a setting?

  2. orbalon
    Posted 7 years ago #

    I noticed something else...

    On another site (which I know is using super cache. I did a view source and see this as the last line: "<!-- Dynamic Page Served (once) in 1.529 seconds -->".

    Note the "(once)" part?

    On my site, I see this as the last line of the source:
    <!-- Dynamic page generated in 0.854 seconds. -->

    I'm guessing that "(once)" tag has something to do with this?

  3. orbalon
    Posted 7 years ago #

    The previous post appears to be version based after further research.

    Another thing to note:
    When I load a page in firefox (lets say) I can see the cache file being created: "wp-cache-eab2666771bac18604d50f5419c0c7cb.html". Refreshing the page serves that file correctly.

    But then loading the same page up in IE creates another new file:
    Refreshing the page in IE again serves that file correctly.

    After doing that refreshing the Firefox page still serves wp-cache-eab2666771bac18604d50f5419c0c7cb.html until garbage collection comes around or cache is manually cleared.

    So confused...

  4. Donncha O Caoimh
    Posted 7 years ago #

    You're probably logged in as a different user (or not) in each browser. That's why you're seeing this.

  5. orbalon
    Posted 7 years ago #

    I am not logged in as any user when testing this.
    I also tested it from another computer (but on the same network) and had the same issue as described above.

    Any other ideas?

  6. orbalon
    Posted 7 years ago #

    Note, this appeared to be because of a server configuration issue. I moved it to a different server and everything started working fine. (its now on a linux box). The previous box was a dev environment hosted under windows with apache 2.x and php 5. I was also running the site off of a port: 8085 (since I have other sites on that box). Any of these things might have played a role, but I never narrowed it down.

    Hopefully this will lead someone else with the same issue down the right path...

Topic Closed

This topic has been closed to new replies.

About this Topic