Specs rely on expired versions of Structured Headers draft
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Description
draft-yasskin-httpbis-origin-signed-exchanges-impl.md appears to be pinned to Structured Headers draft 10, which expired in April. parser.go looks like it references version 9. draft-yasskin-http-origin-signed-responses.md is not pinned to any particular version, and so generates references to the latest draft (13) when built, but references concepts which do not exist in that draft.
Current versions do not use 'Parameterised List' any more, but the general 'List' structure should suffice for signed-exchanges, likely without any effective syntax changes.
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 draft-yasskin-httpbis-origin-signed-exchanges-impl.md, draft-yasskin-http-origin-signed-responses.md, and parser.go, comparing their Structured Headers references with the current draft. Done means the specifications and parser consistently use current terminology and versions, without relying on expired drafts or concepts absent from the referenced draft.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100