Unclear error processing model for mismatched types
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Description
(Forked from https://github.com/WICG/origin-policy/issues/87#issuecomment-596029083)
https://wicg.github.io/webpackage/draft-yasskin-http-origin-signed-responses.html#name-the-signature-header specifies types for various parameters, but from what I can tell the processing model in https://wicg.github.io/webpackage/draft-yasskin-http-origin-signed-responses.html#section-3.5-7.1.1 does not explain what to do when the types mismatch.
It seems like maybe the intention is to return "invalid", but if so I'd expect an explicit step, like "If integrity is not a string, return "invalid".
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 linked signature-header type definitions and the processing-model section 3.5. Trace each parameter whose type can mismatch and compare the specified behavior with the issue's proposed handling. Done means the processing model explicitly defines the result for mismatched types.
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
- 45/100