browser-cache

问题 REST allows to use etags for caching. Similarly browser supports caching unless headers like the following are set -> maxage, expires, cache-control: private What is difference between etags and the above mentioned caching approach? 回答1: What is difference between etags and normal browser provided caching? I think you will find that they are very different ideas. In HTTP, caching semantics are defined by RFC 7234: Caching. Entity tags are defined by RFC 7232: Conditional Requests An entity

问题 Right now I have OutCache on an action with duration set to 365 days. However depending on some events I would like to clear the cache and there are multiple conditions for clearing cache. Moreover, VaryByParam is not an option. How can I achieve this? I think I can do something like this, store a variable in cookie like: RefreshCache = false and check this in VaryByCustom override method. Incase the RefreshCache evaluates to true, reset it to false, increment VaryByCustom argument variable

问题 Right now I have OutCache on an action with duration set to 365 days. However depending on some events I would like to clear the cache and there are multiple conditions for clearing cache. Moreover, VaryByParam is not an option. How can I achieve this? I think I can do something like this, store a variable in cookie like: RefreshCache = false and check this in VaryByCustom override method. Incase the RefreshCache evaluates to true, reset it to false, increment VaryByCustom argument variable

问题 I have this setting in Chrome devtools: this setting works for me. However, I also want to disable the cache for certain resources. My question is - is there a way to disable the cache for a resource when you use fetch? fetch(url).then(v => {}); is there some option or header that we can use to prevent the browser from using the cache to retrieve the resource? 回答1: This has the answers I was looking for: https://hacks.mozilla.org/2016/03/referrer-and-cache-control-apis-for-fetch/ first make

问题 I have a page with another html page in iframe. In this iframe, i put this header tag <META http-equiv="Pragma" content="no-cache"> <META HTTP-EQUIV="Expires" CONTENT="-1"> <meta http-equiv="cache-control" content="no-cache" /> But chrome still cache it, when iframe content changed, hit f5 button but chrome still load cached version, not new version. Please tell me how to pevent google chrome cache this iframe. 回答1: Set the correct expiry headers in the HTTP response from your server. They

问题 I have a page with another html page in iframe. In this iframe, i put this header tag <META http-equiv="Pragma" content="no-cache"> <META HTTP-EQUIV="Expires" CONTENT="-1"> <meta http-equiv="cache-control" content="no-cache" /> But chrome still cache it, when iframe content changed, hit f5 button but chrome still load cached version, not new version. Please tell me how to pevent google chrome cache this iframe. 回答1: Set the correct expiry headers in the HTTP response from your server. They

问题 I've read about single cache-control header value. To test what I learned, I opened facebook and inspect. This is the Cache-Control response header I get: cache-control:private, no-cache, no-store, must-revalidate I am confused what this header actually tells, because it contains 4 values at once. So what happens with the resource send through the network, if it contains such header? EDIT: no-store says, "do not store at all, not in private not public caches", and no-cache says "yeees you can

问题 I've read about single cache-control header value. To test what I learned, I opened facebook and inspect. This is the Cache-Control response header I get: cache-control:private, no-cache, no-store, must-revalidate I am confused what this header actually tells, because it contains 4 values at once. So what happens with the resource send through the network, if it contains such header? EDIT: no-store says, "do not store at all, not in private not public caches", and no-cache says "yeees you can

问题 I've read about single cache-control header value. To test what I learned, I opened facebook and inspect. This is the Cache-Control response header I get: cache-control:private, no-cache, no-store, must-revalidate I am confused what this header actually tells, because it contains 4 values at once. So what happens with the resource send through the network, if it contains such header? EDIT: no-store says, "do not store at all, not in private not public caches", and no-cache says "yeees you can

问题 The Problem I have a problem with cached Vue.js components and I can't reproduce this problem on my devices but every client-side update we get users complains about broken interfaces and only clearing browser cache helps. I use Laravel + Vue.js and it's multipage app. Strategy All components described in one file which included in app.js and it looks like this: Vue.component('task-feed', () => import('./components/task/task-feed'/* webpackChunkName: "/js/components/task-feed" */)); Vue