WordPress.org

Ready to get started?Download WordPress

Forums

[resolved] [Plugin: WP Super Cache] Different files for different browsers? (6 posts)

  1. thegunninghawk
    Member
    Posted 4 years ago #

    Good morning.

    I installed this plugin yesterday, it works and I'm grateful for that but I tested it on three different browsers:

    1. Firefox 3.5 on my local PC
    2. IE 7 on my local PC
    3. IE 6 via remoting on a server

    What I found strange - but maybe not that strange - is that the three of them, at the very bottom of the same page show a different timestamp.

    Is this normal?

    Thank you.

  2. Donncha O Caoimh
    Member
    Posted 4 years ago #

    Did you leave comments using one browser, logged in on another, and not logged in or leave comments on the third?

  3. thegunninghawk
    Member
    Posted 4 years ago #

    I am logged in in Firefox, not in IE7, not in IE6. What I did in IE6 and IE7 was to enter the page and view source. No log-in, no comments. Allow to me to take advantage of your kind help to ask some more questions:

    1. What determines when to invalidate the cache? I understand when a comment is posted, that makes sense, but I've seen pages being invalidated despite no comments were posted. Example this morning I scheduled an article at 04:00, I entered the page at 09:30 and the timestamp was indeed 09:30.

    2. I am on IIS6 and the settings page is saying "Mod rewrite may not be installed!". What exactly is this? Permalinks are still working properly and caching is in place.

    3. Lock Down. Apologies if a stupid question but what exactly does this feature do? I have occasions when I get 2,000+ hits in a matter of seconds on a particular article. What I was going to do is to disable comments, so as to be 100% sure that the page is always retrieved from the cache. Is Lock Down a "similar" feature?

    Thank you.

  4. thegunninghawk
    Member
    Posted 4 years ago #

    First and only bump.

    Thanks.

  5. Donncha O Caoimh
    Member
    Posted 4 years ago #

    1. Actions like posting a comment invalidate the cache but also time. That's why there's an expiry time. The timestamp was 9.30 probably because you're logged in and the cache file was generated just for you. Or you don't get much traffic and you were the first visitor.
    2. That's an Apache module. Don't worry about it.
    3. As the admin page says, "When this is enabled, new comments on a post will not refresh the cached static files."

  6. thegunninghawk
    Member
    Posted 4 years ago #

    Million thanks, donncha, topic resolved :)

Topic Closed

This topic has been closed to new replies.

About this Topic