The following errata report has been submitted for RFC6750, "The OAuth 2.0 Authorization Framework: Bearer Token Usage"
-------------------------------------- You may review the report below and at: https://errata.rfc-editor.org/eid9054/ -------------------------------------- Type: Technical Reported by: Jen Kinder <[email protected]> Section 5.1 says: Original Text ------------- Code Content-Type: application/json;charset=UTF-8 Corrected Text -------------- Code Content-Type: application/json Notes ----- JSON’s media type does not allow parameters (RFC 8259). The example in RFC 6750 incorrectly uses: Code application/json;charset=UTF-8 Strict OAuth clients perform exact string equality when validating token responses. Because JSON forbids parameters, the charset version is treated as an unknown media type, causing token parsing to fail. This behavior matches the failure mode described in Errata 6161. Instructions: ------------- This erratum is currently posted as "Reported". Please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party will log in to change the status and edit the report, if necessary. -------------------------------------- RFC6750 (draft-ietf-oauth-v2-bearer) -------------------------------------- Title : The OAuth 2.0 Authorization Framework: Bearer Token Usage Publication Date : October 2012 Author(s) : M. Jones, D. Hardt Category : Proposed Standard Source : oauth (sec) Stream : IETF Verifying Party : IESG _______________________________________________ OAuth mailing list -- [email protected] To unsubscribe send an email to [email protected]
