Ticket #187 (closed design: fixed)
RFC2047 and warn-text
|Reported by:||firstname.lastname@example.org||Owned by:||email@example.com|
|Component:||p6-cache||Severity:||Active WG Document|
P6 still has a normative dependency on RFC 2047: for encoding non-ISO-8859-1 characters in Warn headers:
"The warn-text SHOULD be in a natural language and character set that is most likely to be intelligible to the human user receiving the response. This decision can be based on any available knowledge, such as the location of the cache or user, the Accept-Language field in a request, the Content-Language field in a response, etc. The default language is English and the default character set is ISO-8859-1 ([ISO-8859-1]).
If a character set other than ISO-8859-1 is used, it MUST be encoded in the warn-text using the method described in [RFC2047]."
This should be dropped the same way we already did it for the Reason Phrase (#94).
- Owner set to firstname.lastname@example.org
- Milestone changed from unassigned to 08