`process header` algorithm references undefined fetch response HTTPS state
Open
@clelland is already working on this.
Since Nov 5, 2024.
- Dominant language
- Bikeshed
- Stars
- 84
- Forks
- 39
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 1
Description
In https://w3c.github.io/reporting/#process-header, Step 1 tells us to
Abort these steps if response’s HTTPS state is not "modern", and the origin of response’s url is not potentially trustworthy.
However, the fetch specification does not define the concept of a response's HTTPS state (the link reference is not valid either)
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.
Assessment
This issue has not been assessed yet.