1 |
Hello Alexander |
2 |
|
3 |
On Mon, Nov 13, 2006 at 04:13:07PM +0100, Alexander Skwar wrote: |
4 |
> ) is not a valid character in a URL, though - or is it? |
5 |
|
6 |
According to RFC2396[1], it is: |
7 |
|
8 |
2.3. Unreserved Characters |
9 |
|
10 |
Data characters that are allowed in a URI but do not have a reserved |
11 |
purpose are called unreserved. These include upper and lower case |
12 |
letters, decimal digits, and a limited set of punctuation marks and |
13 |
symbols. |
14 |
|
15 |
unreserved = alphanum | mark |
16 |
|
17 |
mark = "-" | "_" | "." | "!" | "~" | "*" | "'" | "(" | ")" |
18 |
|
19 |
Unreserved characters can be escaped without changing the semantics |
20 |
of the URI, but this should not be done unless the URI is being used |
21 |
in a context that does not allow the unescaped character to appear. |
22 |
|
23 |
So, foo/(123)/ is valid. ASP.NET makes use of this to include the |
24 |
session ID in the URL. Not really on topic here, but it's the only place |
25 |
where I've seen parentheses in URLs. |
26 |
|
27 |
Greets, |
28 |
Michael |
29 |
|
30 |
[1] http://www.ietf.org/rfc/rfc2396.txt |
31 |
|
32 |
-- |
33 |
Gentoo Linux developer, http://hansmi.ch/, http://forkbomb.ch/ |