- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Thu, 04 Aug 2005 12:19:48 +0200
- To: Robert Collins <robertc@robertcollins.net>
- CC: HTTP Working Group <ietf-http-wg@w3.org>
Robert Collins wrote: > Hi, > trying to determine the correct method to encode unicode characters > into URI's in the Location: header.... > > std66 says that *new* URI Schemes should allow require UCS characters to > be encoded as utf8, and then those that fall outside the unreserved set > to be percent escaped. > > The http:// scheme is as far as I can determine (maybe my google juice > is failing me) specified by rfc2616 which doesn't mention UCS at all - > it predate std66 by quite some time. > > So: what is the correct encoding approach for non US-ASCII characters in > HTTP URI's in Location: ? What does this have to do with "Location"? A URI never ever contains non-ASCII characters, no matter where it appears. That being said; the *best* way (if you control the server) to embed non ASCII data into a URI usually is to UTF-8 encode, then percent-escape. Best regards, Julian
Received on Thursday, 4 August 2005 10:19:57 UTC