FAPI 2.0: x-fapi-* headers
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 3
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Originally submitted by tlodderstedt (Torsten Lodderstedt) on 2020-03-10
The spec currently states the client can send x-fapi headers, but does not give a rationale nor describes what is the AS supposed to do with those headers. Please plarify.
Bitbucket status: open
Bitbucket origin: issue 282
Contributor guide
No contributing guide indexed for this repository
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 FAPI 2.0 specification passages covering the x-fapi-* headers and review the issue discussion for the unresolved points. Clarify why clients send these headers and specify what the authorization server is expected to do with them; the issue is complete when the specification states both unambiguously.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100