OCSP fetches bypass service worker
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 2.3k
- Forks
- 403
- Avg merge
- 21h 16m
- Merged PRs (30d)
- 4
Description
- We moved this issue from service worker to fetch. The OP is https://github.com/slightlyoff/ServiceWorker/issues/564.
During the SW f2f, we confirmed that it shouldn't go through SW: https://github.com/slightlyoff/ServiceWorker/issues/564#issuecomment-235893206.
Fetch seems a right place to either monkey patch or leave non-normative comments at this time.
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 the referenced ServiceWorker issue 564 and its linked face-to-face comment, then review how the Fetch Standard addresses OCSP requests. The issue is done when the Fetch-side treatment is specified, either through a monkey-patch direction or a non-normative comment.
Written by the indexing model from the issue text.
Assessment
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100