W3C home > Mailing lists > Public > www-talk@w3.org > May to June 2001

Default encoding of Request-URI

From: Ronan Daly <ronan.daly@sse.ie>
Date: Thu, 31 May 2001 22:04:08 +0100
Message-ID: <048a01c0ea15$3bbf00c0$422078c1@sse.ie>
To: <www-talk@w3.org>
Apologies if this question has been answered many times, but if it has been,
I can't seem to find the answer.

In RFC 2396 section 2.1 paragraph 7 it states that

"Internet protocols that
   transmit octet sequences intended to represent character sequences
   are expected to provide some way of identifying the charset used"

and

"An individual URI scheme may require a single
   charset, define a default charset, or provide a way to indicate the
   charset used."

Request-URI (Sec 5.1.2) as defined in RFC 2616 relies on constructs taken
from 2396. However it doesn't seem to state what the encoding is from octet
sequence to characters. I have seen Latin-1 and US-ASCII pop up as default
encoding schemes. If this is the case, how does one encode paths with
characters that can't be represented in these schemes?

Thanks for any help.

--
Ronan
Received on Thursday, 31 May 2001 17:04:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 October 2010 18:14:26 GMT