- From: Anne van Kesteren <annevk@opera.com>
- Date: Thu, 10 Feb 2011 09:40:29 +0100
- To: Martin J. Dürst <duerst@it.aoyama.ac.jp>, "Mark Nottingham" <mnot@mnot.net>
- Cc: "httpbis Group" <ietf-http-wg@w3.org>, "Julian F. Reschke" <julian.reschke@gmx.de>
On Thu, 10 Feb 2011 02:30:47 +0100, Mark Nottingham <mnot@mnot.net> wrote: > I suggest calling such headers explicitly invalid so that receivers who > choose to implement error handling (as per the previous thread I started > recently) have a "hook" to do so; i.e., if a string fails to decode as > 8859-1, they can implement error handling to try it as UTF-8. It's not > particularly elegant to do it this way, but it is workable given the > constraints we have. Decoding as ISO-8859-1 cannot fail. Each byte maps to a character. I have not checked recently, but the Location header might be decoded as UTF-8 in some clients. -- Anne van Kesteren http://annevankesteren.nl/
Received on Thursday, 10 February 2011 08:41:11 UTC