Re: Warn header (P6) vs RFC2047 encoding

Tracking in <>

On 23/07/2009, at 8:22 PM, Julian Reschke wrote:

> Hi,
> I noticed that 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]." -- < 
> >
> I think this should be dropped the same way we already did it for  
> the Reason Phrase (see < 
> >).
> Best regards, Julian

Mark Nottingham

Received on Friday, 24 July 2009 06:02:53 UTC