Opened 14 years ago
Closed 13 years ago
#173 closed design (fixed)
CR and LF in chunk extension values
Reported by: | mnot@… | Owned by: | |
---|---|---|---|
Priority: | urgent | Milestone: | 08 |
Component: | p1-messaging | Severity: | Active WG Document |
Keywords: | Cc: |
Description
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).
Attachments (1)
Change History (10)
comment:1 Changed 14 years ago by mnot@…
- Priority set to normal
comment:2 Changed 14 years ago by mnot@…
- Priority changed from normal to urgent
comment:3 Changed 13 years ago by mnot@…
No objection to proposal in the room at Stockholm meeting
comment:4 Changed 13 years ago by mnot@…
- Milestone changed from unassigned to 08
comment:5 Changed 13 years ago by mnot@…
1) Replace OWS in qdtext with space and tab, and 2) Remove obs-text from qdtext, and 3) Restrict quoted-text to VCHAR.
comment:6 Changed 13 years ago by julian.reschke@…
comment:7 Changed 13 years ago by julian.reschke@…
comment:8 Changed 13 years ago by julian.reschke@…
comment:9 Changed 13 years ago by mnot@…
- Resolution set to fixed
- Status changed from new to closed
Proposal: remove /r /n from quoted-string altogether (i.e., in all uses, not just chunk-ext)