Opened 15 years ago
Closed 14 years ago
#74 closed design (fixed)
Character Encodings in TEXT
Reported by: | mnot@… | Owned by: | |
---|---|---|---|
Priority: | Milestone: | 07 | |
Component: | p6-cache | Severity: | |
Keywords: | Cc: |
Description (last modified by mnot@…)
RFC 2616 prescribes that headers containing non-ASCII have to use either iso-8859-1 or RFC 2047. This is unnecessarily complex and not necessarily followed by implementations or by specifications of new headers.
This issue is limited to:
- determining whether UTF-8 can be allowed in some way (e.g., in current uses of TEXT, and/or new headers), and
- possibly tightening up use of iso-8859-1 in TEXT (in particular, C1 controls).
Change History (12)
comment:1 Changed 15 years ago by mnot@…
- Component set to messaging
- Milestone set to unassigned
comment:2 follow-up: ↓ 3 Changed 15 years ago by mnot@…
- Summary changed from Character encodings for Headers to Encodings for non-ASCII Headers
comment:3 in reply to: ↑ 2 Changed 15 years ago by julian.reschke@…
Replying to mnot@pobox.com:
There was discussion of this at the APPS Area Architecture Workshop, with some disagreement as to whether it's possible to encode IRI->URI->IRI. Specific advice to IRIs may be necessary.
Is this about round-tripping IRIs through URIs? Obviously that's not possible.
For example, consider the two IRIs:
I1: http://www.example.org/Dürst
I2: http://www.example.org/D%C3%BCrst
Both would be converted to the URI:
U: http://www.example.org/D%C3%BCrst
Now whether that disctinction is relevant of course depends on which kind of URI/IRI comparison is needed; but there are cases where it is relevant (for instance, XML namespace names using IRIs (urg!)).
(see also http://tools.ietf.org/html/rfc3987#section-3.2.1)
comment:4 Changed 15 years ago by mnot@…
- Description modified (diff)
- Summary changed from Encodings for non-ASCII Headers to Character Encodings in TEXT
comment:5 Changed 15 years ago by mnot@…
- Description modified (diff)
comment:6 Changed 15 years ago by mnot@…
- Description modified (diff)
comment:7 Changed 14 years ago by mnot@…
- Milestone changed from unassigned to 06
comment:8 Changed 14 years ago by fielding@…
comment:9 Changed 14 years ago by julian.reschke@…
- Resolution set to fixed
- Status changed from new to closed
comment:10 Changed 14 years ago by julian.reschke@…
- Resolution fixed deleted
- Status changed from closed to reopened
re-open until reviewed
comment:11 Changed 14 years ago by julian.reschke@…
- Component changed from p1-messaging to p6-cache
- Milestone changed from 06 to 07
Part 6 still allows RFC2047 encoding for the Warn header.
comment:12 Changed 14 years ago by mnot@…
- Resolution set to fixed
- Status changed from reopened to closed
There was discussion of this at the APPS Area Architecture Workshop, with some disagreement as to whether it's possible to encode IRI->URI->IRI. Specific advice to IRIs may be necessary.