Reason-Phrase BNF

[mnot@…]

Looking at...:

TEXT           = <any OCTET except CTLs, but including LWS>
LWS            = [CRLF] 1*( SP | HT )
CRLF           = CR LF

Reason-Phrase  = *<TEXT, excluding CR, LF>

So was the real intent to say: any OCTET except CTLs?

[mnot@…]

The plan is to remove the TEXT rule (and associated commentary) altogether, and replace it with instances that call out the specific legal octets and how to interpret them.

They are;

1) field-content (p1)

---8<---

field-content = *( VCHAR / WSP / obs-text ) obs-text = %x80-FF

Historically, HTTP has allowed field-content with text in the ISO-8859-1 charset (allowing other charsets through use of RFC2047 encoding). In practice, most HTTP header field-values are a subset of the ASCII charset, and newly defined headers SHOULD constrain their field-values to ASCII characters. Recipients SHOULD treat obs-text characters in header field-content as raw octets. --->8---

2) comment (p1)

---8<--- ctext = *( OWS / %x21-27 / %x2A-7E / obs-text ) --->8---

Note that OWS is Optional White Space, like LWS (work in progress).

3) quoted-string

---8<--- qdtext = *( OWS / %x21 / %x23-5B / %x5D-7E / obs-text ) --->8---

4) reason-phrase (p1/p2)

---8<--- Reason-Phrase = *( VCHAR / WSP / obs-text ) --->8---

Note that this also resolves the editorial issue #94 (Reason-Phrase BNF).

[fielding@…]

From [395]:

Deprecate line folding, addresses #77. Require that invalid whitespace around field-names be rejected, addresses #30. Make non-ASCII content obsolete and opaque in header fields and reason phrase, addresses #63, #74, #94, #111.

[julian.reschke@…]

Fixed in [398]:

Resolve #63, #74, #94, #111: Issues around TEXT rule closed with revision [395] (closes #63, #74, #94, #111)

[julian.reschke@…]

re-open until reviewed