W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2008

Re: IRIs, IDNAbis, and HTTP

From: Henrik Nordstrom <henrik@henriknordstrom.net>
Date: Tue, 18 Mar 2008 16:08:07 +0100
To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Cc: ietf-http-wg@w3.org
Message-Id: <1205852887.18425.96.camel@HenrikLaptop>

On Mon, 2008-03-17 at 06:21 +0100, Frank Ellermann wrote:
> No.  It would need to be something that's displayed, parsed,
> voice output, dunno, anything where the language or script
> helps.  Excluding eur-EU, mis-EA, zxx-DG, und-IC, etc. <eg>

In HTTP about the only unstructured protocol field really meant to be
displayed is the human intended status code description. Where most uses
the suggested texts found in 2616.

But the authentication schemes (2617) need to tackle encodings one way
or antother. Today HTTP authentication only allows iso-8859-1 in
usernames or passwords.. 

Well, the character set is not at all defined for digest passwords, but
iso-8859-1 for all else, inherited from the definition of TEXT in 2616.

Received on Tuesday, 18 March 2008 15:09:34 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:10:45 UTC