cache API put should read internal response body of filtered responses
Open
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 3.6k
- Forks
- 324
- Avg merge
- 14d 22h
- Merged PRs (30d)
- 1
Description
Step 11.1 of cache put:
https://w3c.github.io/ServiceWorker/#cache-put
Tries to get the body stream of the response in order to drain it. This does not work properly if the response is an opaque filtered response since the body is hidden. The algorithm should instead get the body of the filtered internal response.
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 with Step 11.1 of the Cache put algorithm in the linked Service Worker specification and review how it obtains a response body. Confirm the behavior for opaque filtered responses, then update the algorithm so it reads the filtered response's internal body; done when the step correctly drains that body.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100