Ticket #20 (closed design: fixed)
Default charsets for text media types
|Reported by:||firstname.lastname@example.org||Owned by:||email@example.com|
|Component:||p3-payload||Severity:||Active WG Document|
2616 Section 3.7.1 states;
When no explicit charset parameter is provided by the sender, media subtypes of the "text" type are defined to have a default charset value of "ISO-8859-1" when received via HTTP.
However, many, if not all, of the text/* media types define their own defaults; text/plain (RFC2046), for example, defaults to ASCII, as does text/xml (RFC3023).
How do these format-specific defaults interact with HTTP's default? Is HTTP really overriding them?
I'm far from the first to be confused by this text, and I'm sure it's been asked before, but I haven't been able to find a definitive answer. If errata are still being considered, perhaps removing/ modifying this line would be a good start...
- version set to d00
- Component set to payload
- Milestone set to unassigned
- Milestone changed from unassigned to 02
comment:15 Changed 5 years ago by firstname.lastname@example.org
- Priority changed from normal to later
- Severity set to Active WG Document
comment:21 Changed 4 years ago by email@example.com
- Status changed from new to closed
- Resolution set to incorporated
comment:23 Changed 4 years ago by firstname.lastname@example.org
- Status changed from closed to reopened
- Resolution incorporated deleted
comment:24 Changed 4 years ago by email@example.com
- Status changed from reopened to closed
- Resolution set to fixed