Msg#: 4154605 posted 6:33 am on Jun 18, 2010 (gmt 0)
How does one guarantee that the latest changes to the website will be served to browsers instead of browser just using the cached version?
I mean, we look at news websites and we don't read old news everyday. We can trust our browsers that they are picking up the latest changes to the news website.
But when I have changed my website, my mate can't see the changes. There must be some file or code you put in a website to "push" the browser to not serve the cached version, but get the latest version off the server.
Msg#: 4154605 posted 1:23 pm on Jun 21, 2010 (gmt 0)
more info would be appreciated. also even a reference to a good book or website that talks about this stuff.
Msg#: 4154605 posted 9:35 pm on Oct 9, 2010 (gmt 0)
I have used the method: <META HTTP-EQUIV="PRAGMA" CONTENT="NO-CACHE"> and that usually seems to work. Recently I learned about this one though: <meta http-equiv="cache-control" content="no-store" />
Supposedly it tells the browser to store the web page in its cache temporarily, but if you leave the site and come back it will load the fresh version again (instead of saving the cached version.) Anyone know anything about that?