should FetchEvent.request.cache reflect non-fetch browser cache controls?
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 3.6k
- Forks
- 324
- Avg merge
- 14d 22h
- Merged PRs (30d)
- 1
Description
Currently the Request.cache attribute reflects the request's RequestCache setting. The current specs are a bit vague on this point. Only fetch() actually sets this, but the browser can bypass the http cache for other reasons. For example, if a user presses the refresh button causing the page to reload with http cache revalidation, should the corresponding FetchEvent.request.cache be set to no-cache.
I believe we should reflect these browser cache settings on all FetchEvent's whether they come from fetch() or another source.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the current definition of FetchEvent.request.cache and how cache behavior differs between fetch() requests and browser-initiated reloads or revalidations. Resolve the intended mapping for non-fetch browser cache controls, then update the relevant specification text and add coverage for both request sources.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100