search

httpwg / httpbis-issues

1 stars 1 forks source link

RFC2047 and warn-text #187

Closed mnot closed 3 years ago

mnot commented 15 years ago

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).

Reported by @mnot, migrated from https://trac.ietf.org/trac/httpbis/ticket/187

mnot commented 15 years ago

agreed to remove 2046 encoding, but take it to the mailing list

mnot commented 15 years ago

Proposed patch for part 6.

mnot commented 15 years ago

Proposed patch for part 6.

mnot commented 15 years ago

julian.reschke@gmx.de changed status from new to assigned

mnot commented 15 years ago

julian.reschke@gmx.de commented:

From 669:

Remove mentions of character encoding and language in description of Warning header (see #187)

mnot commented 15 years ago