- From: Yves Lafon <ylafon@w3.org>
- Date: Fri, 19 Feb 2010 16:59:49 -0500 (EST)
- To: Douglas Perreault CPA* CITP <doug@perreault.us>
- cc: www-validator-css@w3.org
On Fri, 19 Feb 2010, Douglas Perreault CPA* CITP wrote:
> You note below that the URL in the first instance is
> "images/Richland_College.jpg;",
>
> However, it is my understanding that the semicolon is a reserved character.
> Therefore, for this to have been a valid URL it would have to have had the
> semicolon encoded. See http://www.faqs.org/rfcs/rfc1738.html, Section 2.2.
> It notes:
>
> ------
> Thus, only alphanumerics, the special characters "$-_.+!*'(),", and reserved
> characters used for their reserved purposes may be used unencoded within a
> URL.
> ------
unreserved = ALPHA / DIGIT / "-" / "." / "_" / "~"
But...
reserved = gen-delims / sub-delims
gen-delims = ":" / "/" / "?" / "#" / "[" / "]" / "@"
sub-delims = "!" / "$" / "&" / "'" / "(" / ")"
/ "*" / "+" / "," / ";" / "="
If reserved characters were always urlencoded,
http://www.example.com/foo/bar would be illegal.
Fortunately
pchar = unreserved / pct-encoded / sub-delims / ":" / "@"
Gives the anwser: http://www.example.com/foo; is perfectly legal, as ";"
is in sub-delims.
So Damien was entirely right in his analysis.
Cheers,
--
Baroula que barouleras, au tiéu toujou t'entourneras.
~~Yves
Received on Friday, 19 February 2010 21:59:50 UTC