Extend Accept-Signature to include app/s-e response type
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Description
The Accept-Signature header says:
When a server receives an
Accept-Signatureheader field in a client request, it SHOULD reply with any availableSignatureheader fields for its response that theAccept-Signatureheader field indicates the client supports.
However, the same-origin Signature response may be less reliable than application/signed-exchange, due to possible undesired transformations of signed data (headers or payload). Consider modifying this section to say that a server MAY reply with an application/signed-exchange instead.
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
Read the Accept-Signature section in the linked Web Packaging specification and compare its current wording with the requested behavior. Done means the section clearly allows a server to respond with an application/signed-exchange when appropriate, with the specification text updated accordingly.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100