Stas Bekman wrote:
> According to the RFC 2396: http://www.faqs.org/rfcs/rfc2396.html
> uric = reserved | unreserved | escaped
> reserved = ";" | "/" | "?" | ":" | "@" | "&" | "=" | "+" |
> "$" | ","
> unreserved = alphanum | mark
> mark = "-" | "_" | "." | "!" | "~" | "*" | "'" |
> "(" | ")"
>
> escaped = "%" hex hex
> hex = digit | "A" | "B" | "C" | "D" | "E" | "F" |
> "a" | "b" | "c" | "d" | "e" | "f"
>
> so "/" is not a problem.
why ?
i can see that "/" (like "&") is reserved, thus should be
escaped, no?
./allan
...
2.2. Reserved Characters
Many URI include components consisting of or delimited
by, certain
special characters. These characters are called
"reserved", since
their usage within the URI component is limited to their reserved
purpose. If the data for a URI component would conflict
with the
reserved purpose, then the conflicting data must be
escaped before
forming the URI.
reserved = ";" | "/" | "?" | ":" | "@" | "&" | "="
| "+" |
"$" | ","
The "reserved" syntax class above refers to those
characters that are
allowed within a URI, but which may not be allowed within a
particular component of the generic URI syntax; they are
used as
delimiters of the components described in Section 3.
Characters in the "reserved" set are not reserved in all contexts.
The set of characters actually reserved within any given URI
component is defined by that component. In general, a
character is
reserved if the semantics of the URI changes if the
character is
replaced with its escaped US-ASCII encoding.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
