Clik here to view.
Cache API for Cloudflare Workers - Beta Feedback
@ryan wrote: The Cache API gives you fine grained control of reading and writing from cache, and deciding exactly when to fetch data from your origin. This API is strongly influenced by the web...
View ArticleCache API for Cloudflare Workers - Beta Feedback
@rmaidment wrote: Hi, I’m no Javascript expert so I may be missing something, but what is the purpose of this line in the “Add Cache-Tag To Response” example in the docs? response = new...
View ArticleClik here to view.
Cache API for Cloudflare Workers - Beta Feedback
@martin2 wrote: Responses are treated as a stream, so they can only be read once. This is why you see responses being cloned, or constructed into new responses. Mainly because of memory efficiency. In...
View ArticleClik here to view.
Cache API for Cloudflare Workers - Beta Feedback
@adaptive wrote: So far the experience with the Cache API has been coherent and stable, with the addition of Workers KV it is a bliss. For me, it only makes sense using the two together: Without...
View ArticleCache API for Cloudflare Workers - Beta Feedback
@rmaidment wrote: When I put a response in cache it has these headers: cache-control: public, max-age=30 cache-tag: blah content-type: text/plain When I read it out again, it has these headers:...
View ArticleClik here to view.
Cache API for Cloudflare Workers - Beta Feedback
@adaptive wrote: @rmaidment You need to change Browser Cache Expiration on the dashboard to Respect Existing Header. It should fix your issue. Screenshot 2018-10-12 at 00.46.16.png2066×1830 335 KB...
View Article
