[OAUTH-WG] [Editorial Errata Reported] RFC6749 (7716)

RFC Errata System <rfc-editor@rfc-editor.org> Wed, 29 November 2023 16:56 UTC

To: rfc-editor@rfc-editor.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: hello@alexwilson.io, dick.hardt@gmail.com, oauth@ietf.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20231129165633.15B4418EF1DF@rfcpa.amsl.com>
Date: Wed, 29 Nov 2023 08:56:33 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/h4DU-xG6eSYBvKQA9xZPqT1RHwE>
Subject: [OAUTH-WG] [Editorial Errata Reported] RFC6749 (7716)
Precedence: list

The following errata report has been submitted for RFC6749,
"The OAuth 2.0 Authorization Framework".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7716

--------------------------------------
Type: Editorial
Reported by: Alex Wilson <hello@alexwilson.io>

Section: 4.2.2

Original Text
-------------
   For example, the authorization server redirects the user-agent by
   sending the following HTTP response (with extra line breaks for
   display purposes only):

     HTTP/1.1 302 Found
     Location: http://example.com/cb#access_token=2YotnFZFEjr1zCsicMWpAA
               &state=xyz&token_type=example&expires_in=3600


Corrected Text
--------------
   For example, the authorization server redirects the user-agent by
   sending the following HTTP response (with extra line breaks for
   display purposes only):

     HTTP/1.1 302 Found
     Location: http://client.example.com/cb?access_token=2YotnFZFEjr1zCsicMWpAA
               &state=xyz&token_type=example&expires_in=3600


Notes
-----
- Host example.com should be client.example.com to be consistent with other examples.
- A hash is used for the query parameters when a question mark should have been used.

Instructions:
-------------
This erratum is currently posted as "Reported". (If it is spam, it 
will be removed shortly by the RFC Production Center.) 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.

--------------------------------------
RFC6749 (draft-ietf-oauth-v2-31)
--------------------------------------
Title               : The OAuth 2.0 Authorization Framework
Publication Date    : October 2012
Author(s)           : D. Hardt, Ed.
Category            : PROPOSED STANDARD
Source              : Web Authorization Protocol
Area                : Security
Stream              : IETF
Verifying Party     : IESG

[OAUTH-WG] [Editorial Errata Reported] RFC6749 (7… RFC Errata System
Re: [OAUTH-WG] [Editorial Errata Reported] RFC674… Brian Campbell
Re: [OAUTH-WG] [Editorial Errata Reported] RFC674… Rebecca VanRheenen