IETF Logo Mail Archive

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

"Clive D.W. Feather" <clive@demon.net> Mon, 20 August 2007 10:29 UTC

Return-path: <discuss-bounces@apps.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IN4VO-0006mZ-Jf; Mon, 20 Aug 2007 06:29:06 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1IN4VN-0006mU-Rg for discuss-confirm+ok@megatron.ietf.org; Mon, 20 Aug 2007 06:29:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IN4VN-0006mM-Hz for discuss@apps.ietf.org; Mon, 20 Aug 2007 06:29:05 -0400
Received: from anchor-internal-1.mail.demon.net ([195.173.56.100]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IN4VM-0008EQ-7k for discuss@apps.ietf.org; Mon, 20 Aug 2007 06:29:05 -0400
Received: from finch-staff-1.server.demon.net (finch-staff-1.server.demon.net [193.195.224.1]) by anchor-internal-1.mail.demon.net with ESMTP id l7KASsf4010817Mon, 20 Aug 2007 10:29:03 GMT
Received: from clive by finch-staff-1.server.demon.net with local (Exim 3.36 #1) id 1IN3Qk-000JfX-00; Mon, 20 Aug 2007 10:20:14 +0100
Date: Mon, 20 Aug 2007 10:20:14 +0100
From: "Clive D.W. Feather" <clive@demon.net>
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: Character encodings in headers [i74][was: Straw-man charter for http-bis]
Message-ID: <20070820092014.GH68079@finch-staff-1.thus.net>
References: <BA772834-227A-4C1B-9534-070C50DF05B3@mnot.net> <392C98BA-E7B8-44ED-964B-82FC48162924@mnot.net> <p06240843c2833f4d7f2f@[10.20.30.108]> <465D9142.9050506@gmx.de> <6.0.0.20.2.20070610165356.0a69cec0@localhost> <088FB13E-F12F-4BE7-94FB-78B21C51512E@mnot.net> <157F4F253535B9C73F8EDC75@p3.JCK.COM> <6B8E3D7A-71B8-4B8D-9625-2AB3C74A9072@mnot.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <6B8E3D7A-71B8-4B8D-9625-2AB3C74A9072@mnot.net>
User-Agent: Mutt/1.5.3i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: Paul Hoffman <phoffman@imc.org>, 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>
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org

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

v2.23.0 | Report a Bug | By Email