Re: [w3c/ServiceWorker] The Cache objects do not expire unless authors *or users* delete the entries. (#1276)

Is there a use case for supporting the `Expires` or `Cache-Control` headers or setting expiration against the CacheStorage API

Our use-case is currently PWA Audio tours which can contain >1gb of cache controlled content & if the user leaves the page without requesting the PWA to delete any content, then according to the spec that space persists & the browser will not remove this.

Having some eviction criteria against the CacheStorage would allow the browser to remove Cache Responses in the absence of the service-worker



-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1276#issuecomment-1050736855
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/ServiceWorker/issues/1276/1050736855@github.com>