Garth Wallace wrote:
>
> But if they're adding the
> ">" to the actual URL, they're violating section 2.2 of the RFC,
> which states that "<" and ">" are among the "unsafe"
> characters that must not appear unescaped in a URL:
>
Which is why it is suggested that "<" and ">" can be used to safely
delimit the start and end of the URL; they're not valid characters in
the URL.
Have a look at RFC 2396, Section 2.4.3:
"The angle-bracket "<" and ">" and double-quote (") characters are
excluded because they are often used as the delimiters around URI in
text documents and protocol fields."
The further down in Appendix E, Recommendations for Delimiting URI in
Context:
"In practice, URI are delimited in a variety of ways, but usually
within double-quotes "http://test.com/";, angle brackets
<http://test.com/>, or just using whitespace ..."
So I'd say it's fine to use them (and without the "URL:" prefix).
--
? Mike Gratton - [EMAIL PROTECTED]
! Leader in leachate production and transmission since 1976.
> http://web.vee.net/
