browser-cache

问题 Which browsers nowadays support a back-forwards cache (bfcache)? A back-forwards cache is a browser's in-memory cache that is used when a user clicks the back button and the forward button. It stores the state of the page as it was when the user navigated away, so any changes made to the DOM should be loaded instantly. Note that this is different from the normal caching mechanisms that all browsers have. A bfcache applies specifically when a user clicks the back button, and can handle dynamic

问题 When I look at this published Google Docs document, I see the latest version with Firefox and Chrome , but an older version with IE8 . Also, screen-scraping it via PHP/Curl gives me an older version. I've tried CTRL-Refresh in IE8 but I can't get it to show me the newest version. No matter what headers I try to change in PHP/Curl, I can't get it to show me the newest version. Note: I'm sure I could dig in IE8 and find some cache entry to clear, but what is not happening on this URL that is

问题 When I look at this published Google Docs document, I see the latest version with Firefox and Chrome , but an older version with IE8 . Also, screen-scraping it via PHP/Curl gives me an older version. I've tried CTRL-Refresh in IE8 but I can't get it to show me the newest version. No matter what headers I try to change in PHP/Curl, I can't get it to show me the newest version. Note: I'm sure I could dig in IE8 and find some cache entry to clear, but what is not happening on this URL that is

问题 This is a follow-up to a previous question where the answer to "How do I ensure I see the latest JS code in my Task Pane add-in" involved controlling the client side caching behavior via server-added meta/no-cache tags (or versioning the server resources). However, I am looking for a manual way, on the client , for the end-user to clear out the client side cache that appears to be storing JavaScript files and preventing an updated JS file on the server from being used by the Task Pane add-in.

问题 I am attempting to build a "version updated" component that will show a banner when the website has been updated and prompt a user to reload. Unfortunately when some users reload their page is cached so it does not update properly. Previously we have told them to press CTRL+F5 but I am looking for a way to do this programatically. I am using the following code this.$window.location.reload(true); Whose function signature is declared like so: reload(forcedReload?: boolean): void; Does this mean

问题 I am attempting to build a "version updated" component that will show a banner when the website has been updated and prompt a user to reload. Unfortunately when some users reload their page is cached so it does not update properly. Previously we have told them to press CTRL+F5 but I am looking for a way to do this programatically. I am using the following code this.$window.location.reload(true); Whose function signature is declared like so: reload(forcedReload?: boolean): void; Does this mean

问题 I am attempting to build a "version updated" component that will show a banner when the website has been updated and prompt a user to reload. Unfortunately when some users reload their page is cached so it does not update properly. Previously we have told them to press CTRL+F5 but I am looking for a way to do this programatically. I am using the following code this.$window.location.reload(true); Whose function signature is declared like so: reload(forcedReload?: boolean): void; Does this mean

问题 A website was accidentally cached in the browser for about a month with Expires and max-age headers set. The cached resource is text/html and the root / . The freshness validation should work as expected with the If-Modified-Since header in the next request. But somehow a lot of IE users (incl. IE11) don't get the new version anymore, as the browser doesn't make the request. It's easy to bust the cache for resources like CSS, but how to do this for the document/website itself? I can not just

问题 I need to reload the page in Javascript. I use window.location.reload for that purpose. Now, I observe a strange behaviour in Chrome: Chrome always connects to the server and asks if the document was modified. Though a 304 Not Modified is returned, there is still a roundtrip to the server that I want to avoid. I've also tried explicitly using window.location.reload(false) to tell chrome to use the cache, but without success. Not that I have an active hash (#) fragment in the url that I reload

问题 I've noticed something interesting while monitoring the network communications between my browser and server. It has something to do with caching. Say I have a CSS file http://domain.com/main.css (used in unsecured pages), which can also be accessed via https://domain.com/main.css (used in secured pages). When I first load an unsecured page, the CSS file gets a 200 OK . When I reload the page (or go to another unsecured page), I get a 304 Not Modified . When I go to a secured page for the