May a PDP reject a `charset` parameter on the request media type?
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- api, documentation
Research direction
Read §10.1 and RFC 8259 §11, then compare their requirements with the five accept-charset conformance modules described in the issue. Determine whether a PDP must accept parameters on application/json and, if so, propose wording that clarifies the receiving side of §10.1. Done means the standard’s requirement and the modules’ expected behavior are consistent.
Written by the indexing model from the issue text.
Description
Requests MUST include a Content-Type header with the value application/json, and the request body for each endpoint MUST be a JSON object that conforms to the corresponding request structure (spec §10.1)
No "charset" parameter is defined for this registration. Adding one really has no effect on compliant recipients. (RFC 8259 §11)
§10.1 tells the PEP which Content-Type to send; it says nothing about what the PDP must accept. Read literally, application/json; charset=utf-8 is not "the value application/json". RFC 8259 says the parameter has no effect on a compliant recipient, which suggests a PDP should accept it.
Suite today. The five accept-charset modules, one per API plan, send application/json; charset=utf-8 and require HTTP 200 with the fixture result, at FAILURE.
Questions.
- Must a PDP accept parameters on
application/json, such ascharset=utf-8? - If it must, could §10.1 say so for the receiving side, for example by citing RFC 8259 §11?
- Dominant language
- TypeScript
- Stars
- 170
- Forks
- 46
- Avg merge
- 18h 5m
- Merged PRs (30d)
- 43
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from openid/authzen
-
Certification Scenario §7.2.2, §7.3.2 and §7.4.2: identical results, or identical fixture results?Possibly taken @alexolivier claimed this 4 days ago. Openauthorization-api certification
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Search interop runner compares results as JSON strings, so member order decides PASS/FAILMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
openid/authzen#693 · 3 comments ·
Maintainers usually reply within 1 day
-
certification
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
openid/authzen#640 · 1 comment ·
Maintainers usually reply within 1 day
-
access-requests
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
openid/authzen#578 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 35/100
Maintainers usually reply within 1 day
Similar issues
-
🐛 bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LibreChat-AI/LibreChat#17733 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
TypeStrong/typedoc#3150 ·
-
accessibility bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Normalize image-source MIME types before SVG dispatchPossibly taken @HarsH-1877 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
tscircuit/image-utils#58 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
Maintainers usually reply within 2 days