cache-control

问题 RFC 5861 proposes the Cache-Control extensions stale-while-revalidate: When present in an HTTP response, the stale-while-revalidate Cache- Control extension indicates that caches MAY serve the response in which it appears after it becomes stale, up to the indicated number of seconds. and stale-if-error: The stale-if-error Cache-Control extension indicates that when an error is encountered, a cached stale response MAY be used to satisfy the request, regardless of other freshness information.

问题 RFC 5861 proposes the Cache-Control extensions stale-while-revalidate: When present in an HTTP response, the stale-while-revalidate Cache- Control extension indicates that caches MAY serve the response in which it appears after it becomes stale, up to the indicated number of seconds. and stale-if-error: The stale-if-error Cache-Control extension indicates that when an error is encountered, a cached stale response MAY be used to satisfy the request, regardless of other freshness information.

问题 I have one question: suppose in each http request there is a cache-control: max-age=0 header, so each request will go all the way to the origin web server. Does it mean CDN is not useful anymore if all requests are like this? 回答1: By setting the max-age to 0, you effectively expire your page in your CDN edge cache immediately. Therefore, your CDN always hit your origin and render the CDN useless as you suggested. Noticed from your other question that you are using Akamai. If so, then you can

问题 I have one question: suppose in each http request there is a cache-control: max-age=0 header, so each request will go all the way to the origin web server. Does it mean CDN is not useful anymore if all requests are like this? 回答1: By setting the max-age to 0, you effectively expire your page in your CDN edge cache immediately. Therefore, your CDN always hit your origin and render the CDN useless as you suggested. Noticed from your other question that you are using Akamai. If so, then you can

问题 I have one question: suppose in each http request there is a cache-control: max-age=0 header, so each request will go all the way to the origin web server. Does it mean CDN is not useful anymore if all requests are like this? 回答1: By setting the max-age to 0, you effectively expire your page in your CDN edge cache immediately. Therefore, your CDN always hit your origin and render the CDN useless as you suggested. Noticed from your other question that you are using Akamai. If so, then you can

问题 We have an Angular 10 app that everytime we make a deployment to AWS, or even in DEV enviroment(over ngnix) we need to clean cache (CTRL+F5, doing this is solved). We have tried in the Angular project the next meta tags: <meta http-equiv="cache-control" content="no-cache, must-revalidate, post-check=0, precheck=0"> <meta http-equiv="expires" content="0"> <meta http-equiv="pragma" content="no-cache"> Another ideas we have tried is alternating hashing the file names by deployment. Once is done

问题 Is there any use-case where the use of cache-control headers should be preferred over Service Workers? Is there any benefit using both of them (apart from the fact the SW are not cross-browser supported) ? 回答1: Absolutely. HTTP cache, which is controlled by HTTP cache headers sits between the network and the service worker. All fetch requests initiated from the service worker still use HTTP cache. Let's say you have a script with long max-age . Most Service Workers repopulate their caches

问题 Is there any use-case where the use of cache-control headers should be preferred over Service Workers? Is there any benefit using both of them (apart from the fact the SW are not cross-browser supported) ? 回答1: Absolutely. HTTP cache, which is controlled by HTTP cache headers sits between the network and the service worker. All fetch requests initiated from the service worker still use HTTP cache. Let's say you have a script with long max-age . Most Service Workers repopulate their caches

问题 Is there any use-case where the use of cache-control headers should be preferred over Service Workers? Is there any benefit using both of them (apart from the fact the SW are not cross-browser supported) ? 回答1: Absolutely. HTTP cache, which is controlled by HTTP cache headers sits between the network and the service worker. All fetch requests initiated from the service worker still use HTTP cache. Let's say you have a script with long max-age . Most Service Workers repopulate their caches

问题 Is there any use-case where the use of cache-control headers should be preferred over Service Workers? Is there any benefit using both of them (apart from the fact the SW are not cross-browser supported) ? 回答1: Absolutely. HTTP cache, which is controlled by HTTP cache headers sits between the network and the service worker. All fetch requests initiated from the service worker still use HTTP cache. Let's say you have a script with long max-age . Most Service Workers repopulate their caches