Opened 10 years ago

Closed 10 years ago

#187 closed design (fixed)

RFC2047 and warn-text

Reported by: mnot@… Owned by: julian.reschke@…
Priority: normal Milestone: 08
Component: p6-cache Severity: Active WG Document
Keywords: Cc:

Description

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

Attachments (2)

187.diff (4.8 KB) - added by julian.reschke@… 10 years ago.
Proposed patch for part 6.
187.2.diff (4.3 KB) - added by julian.reschke@… 10 years ago.
Proposed patch for part 6.

Download all attachments as: .zip

Change History (6)

comment:1 Changed 10 years ago by julian.reschke@…

  • Milestone changed from unassigned to 08
  • Owner set to julian.reschke@…

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

Changed 10 years ago by julian.reschke@…

Proposed patch for part 6.

Changed 10 years ago by julian.reschke@…

Proposed patch for part 6.

comment:2 Changed 10 years ago by julian.reschke@…

  • Status changed from new to assigned

comment:3 Changed 10 years ago by julian.reschke@…

From [669]:

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

comment:4 Changed 10 years ago by mnot@…

  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.