- From: Martin Duerst <duerst@it.aoyama.ac.jp>
- Date: Sat, 15 Mar 2008 08:26:48 +0900
- To: Julian Reschke <julian.reschke@gmx.de>, Mark Nottingham <mnot@mnot.net>
- Cc: Brian Smith <brian@briansmith.org>, ietf-http-wg@w3.org
At 19:26 08/03/14, Julian Reschke wrote: > >Mark Nottingham wrote: >> Personally, I am *very* -1 on doing this. >> Changing the allowable characters in a protocol element is a *big* change, and there is not an interoperability gain to doing so. >> There is also not a functionality gain; it is possible (if not pretty) to serialise other characters into HTTP headers. > >I think the key question here: is that implemented in practice? (In particular, which encoding?) If yes, fine (and maybe let's document what works). But if not...? Exactly. I'm still waiting for somebody to point to a server that actually serves iso-8859-1 data, or even more, RFC 2045-encoded data. Regards, Martin. #-#-# Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University #-#-# http://www.sw.it.aoyama.ac.jp mailto:duerst@it.aoyama.ac.jp
Received on Monday, 17 March 2008 03:57:01 UTC