Structured Error Messages
Open
Nobody has claimed this yet.
doc: Protocol
topic: resource access
- Dominant language
- HTML
- Stars
- 563
- Forks
- 108
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
In NSS5, we implemented more detailed status messages to give clients more feedback. We should bring this along into the spec.
We have
- 401 Unauthenticated
- 403 User Unauthorized
- 403 Origin Unauthorized
This was not added in #13 and #26 .
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 comparing NSS5's detailed status messages with the specification and reviewing issues #13 and #26. Update the relevant specification section to cover 401 Unauthenticated, 403 User Unauthorized, and 403 Origin Unauthorized, then verify the three cases are represented consistently.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100