W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2007

Re: Character encodings in headers [i74][was: Straw-man charter for http-bis]

From: Clive D.W. Feather <clive@demon.net>
Date: Mon, 20 Aug 2007 10:20:14 +0100
To: Mark Nottingham <mnot@mnot.net>
Cc: John C Klensin <john-ietf@jck.com>, Richard Ishida <ishida@w3.org>, Apps Discuss <discuss@apps.ietf.org>, Felix Sasaki <fsasaki@w3.org>, "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>, Paul Hoffman <phoffman@imc.org>
Message-ID: <20070820092014.GH68079@finch-staff-1.thus.net>

Mark Nottingham said:
> The (potential) problem is that an intermediary (for example) needs  
> to be able to handle headers that it doesn't understand. If it's been  
> built to store headers as iso-8859-1 strings as they pass through (a  
> reasonable assumption, considering 2616), an unknown header with  
> another encoding -- no matter how specified or flagged -- may break it.

On the other hand, the *syntax* allows any valid UTF-8 sequence, since it
doesn't forbid the octets %x80-9F. So it's unlikely that anything will
break unless someone is being very strict in their checking.

-- 
Clive D.W. Feather  | Work:  <clive@demon.net>   | Tel:    +44 20 8495 6138
Internet Expert     | Home:  <clive@davros.org>  | Fax:    +44 870 051 9937
Demon Internet      | WWW: http://www.davros.org | Mobile: +44 7973 377646
THUS plc            |                            |
Received on Monday, 20 August 2007 10:29:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:50:15 GMT