Consider removing or generalizing Accept-Signature identifiers
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Description
Once https://github.com/WICG/webpackage/issues/187 is fixed, the signaling of requested algorithms may be redundant, or worse, ossifying.
It's not clear to me if some signaling may still be useful e.g. whether this is meant for SRI or top-level. Is there harm in the server sending all signatures in all cases?
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 Accept-Signature specification and the discussion in WICG/webpackage#187. Compare whether algorithm identifiers are still needed for SRI or top-level use cases, and document the outcome as a resolved specification decision.
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