CR and LF in chunk extension values

[mnot@…]

A chunk extension value is defined as either token or quoted-string. A

quoted-string allows CRs and LFs for folding and in escaped form under RFC 2616; we have since outlawed the escaped form, and in headers, but not chunk extension values, we now outlaw producing them for folding as- well. Accepting and processing the latter correctly still appears to be a SHOULD level requirement; I am not sure about the former.

It appears that implementations usually just read a line and ignore any- thing after the first ";" character at the beginning of a chunk. Perhaps the specification should use a CRLF-free quoted-string instead for this; if not, the considerations for obs-fold should apply to chunk extension values aswell, or obs-fold should not be used for chunk extension values (which would require a separate quoted-string production aswell).

[mnot@…]

Proposal: remove /r /n from quoted-string altogether (i.e., in all uses, not just chunk-ext)

[mnot@…]

No objection to proposal in the room at Stockholm meeting

[mnot@…]

1) Replace OWS in qdtext with space and tab, and 2) Remove obs-text from qdtext, and 3) Restrict quoted-text to VCHAR.

[julian.reschke@…]

Proposed patch for part 1.

[julian.reschke@…]

From [686]:

disallow all control characters except HTAB in comments and quoted-string (see #173)

[julian.reschke@…]

From [687]:

Undo last change [686] (see #173)

[julian.reschke@…]

From [707]:

Disallow line folding in chunk extensions (see #173)