Support » Plugin: Prevent Browser Caching » Does it actually work?

  • Resolved dccharron

    (@dccharron)


    Many thanks for your plugin. I am lately having a lot of problems with old pages being displayed to repeat visitors. So I am trying your solution.

    In my tests, when I “View Source” I can see how your plugin changes the VER by adding a unique number to the last element. However, if I open another copy of the same page and “View Source”, I often see the same unique number. I thought it was supposed to change each time.

    I can confirm that that the unique number changes each time in Firefox but not in Firefox Private Window. In Chrome, it never seems to change even after I close the browser and re-open it.

    The key question is, does your plugin work at all or does it depend on the browser’s settings? If a browser has “rules” to decide to use a locally cached copy of a page, how will adding a unique number to the VER trigger the browser to download a new copy from the server. The browser is not going to compare that number to the server’s version until it initiates a full download from the server. Why would the browser do that?

    Can you explain how your plugin “convinces” the browser to download a new copy of the page each time? At the moment, based on my own testing using Firefox and Chrome, I don’t think it is working for all mainstream browsers and in all cases.

Viewing 1 replies (of 1 total)
Viewing 1 replies (of 1 total)
  • The topic ‘Does it actually work?’ is closed to new replies.