oauth-v2-1@499a8f8 (original) (raw)

`@@ -59,8 +59,22 @@ normative:

59

`author:

60

`name: "American National Standards Institute"

61

`date: 1986

62

W3C.REC-html401-19991224:

62

WHATWG.URL:

63

title: "URL"

64

target: https://url.spec.whatwg.org/

65

author:

66

ins: WHATWG

67

date: May 2022

63

68

`W3C.REC-xml-20081126:

69

title: "Extensible Markup Language"

70

target: https://www.w3.org/TR/REC-xml/REC-xml-20081126.xml

71

author:

72

ins: T. Bray

73

ins: J. Paoli

74

ins: C. M. Sperberg-McQueen

75

ins: E. Maler

76

ins: F. Yergeau

77

date: November 2008

64

78

65

79

`informative:

66

80

`RFC6265:

`@@ -2028,7 +2042,7 @@ all of the following conditions are met:

2028

2042

2029

2043

`* The content follows the encoding requirements of the

2030

2044

`` application/x-www-form-urlencoded content-type as defined by

2031

HTML 4.01 [W3C.REC-html401-19991224].

2045

the URL Living Standard {{WHATWG.URL}}.

2032

2046

2033

2047

`* The HTTP request content is single-part.

2034

2048

`@@ -3367,8 +3381,8 @@ work is based upon. No changes to those registries are required by this specific

3367

3381

3368

3382

`This section provides Augmented Backus-Naur Form (ABNF) syntax

3369

3383

`descriptions for the elements defined in this specification using the

3370

notation of [RFC5234]. The ABNF below is defined in terms of Unicode

3371

code points [W3C.REC-xml-20081126]; these characters are typically

3384

notation of {{RFC5234}}. The ABNF below is defined in terms of Unicode

3385

code points {{W3C.REC-xml-20081126}}; these characters are typically

3372

3386

`encoded in UTF-8. Elements are presented in the order first defined.

3373

3387

3374

3388

`Some of the definitions that follow use the "URI-reference"

`@@ -3383,7 +3397,7 @@ Some of the definitions that follow use these common definitions:

3383

3397

`%xE000-FFFD / %x10000-10FFFF

3384

3398

3385

3399

`(The UNICODECHARNOCRLF definition is based upon the Char definition

3386

in Section 2.2 of [W3C.REC-xml-20081126], but omitting the Carriage

3400

in Section 2.2 of {{W3C.REC-xml-20081126}}, but omitting the Carriage

3387

3401

`Return and Linefeed characters.)

3388

3402

3389

3403

`` @@ -3515,40 +3529,6 @@ ABNF for code_challenge is as follows.

3515

3529

`DIGIT = %x30-39

3516

3530

3517

3531

3518

Use of application/x-www-form-urlencoded Media Type

3519

-

3520

At the time of publication of this specification, the

3521

`` -

application/x-www-form-urlencoded media type was defined in

3522

Section 17.13.4 of [W3C.REC-html401-19991224] but not registered in

3523

the IANA MIME Media Types registry

3524

(http://www.iana.org/assignments/media-types). Furthermore, that

3525

definition is incomplete, as it does not consider non-US-ASCII

3526

characters.

3527

-

3528

To address this shortcoming when generating contents using this media

3529

type, names and values MUST be encoded using the UTF-8 character

3530

encoding scheme [RFC3629] first; the resulting octet sequence then

3531

needs to be further encoded using the escaping rules defined in

3532

[W3C.REC-html401-19991224].

3533

-

3534

When parsing data from a content using this media type, the names and

3535

values resulting from reversing the name/value encoding consequently

3536

need to be treated as octet sequences, to be decoded using the UTF-8

3537

character encoding scheme.

3538

-

3539

For example, the value consisting of the six Unicode code points

3540

(1) U+0020 (SPACE), (2) U+0025 (PERCENT SIGN),

3541

(3) U+0026 (AMPERSAND), (4) U+002B (PLUS SIGN),

3542

(5) U+00A3 (POUND SIGN), and (6) U+20AC (EURO SIGN) would be encoded

3543

into the octet sequence below (using hexadecimal notation):

3544

-

3545

20 25 26 2B C2 A3 E2 82 AC

3546

-

3547

and then represented in the content as:

3548

-

3549

+%25%26%2B%C2%A3%E2%82%AC

3550

-

3551

-

3552

3532

`# Extensions {#extensions}

3553

3533

3554

3534

`Below is a list of well-established extensions at the time of publication: