[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Prospero and other URLs with // in path

• To: xml-dev@l...
• Subject: Re: Prospero and other URLs with // in path
• From: Pete Forman <pete.forman@w...>
• Date: 25 Jun 2004 10:34:13 +0100
• Organization: WesternGeco, Gatwick, UK
• References: <p06010204bcf33d1deae8@[192.168.254.88]>
• Sender: news <news@s...>
• User-agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Military Intelligence (RC5 Windows))

Elliotte Rusty Harold <elharo@m...> writes:

 > RFC 1738 describes Prospero URLs that look like this:
 > 
 > prospero://host.dom//pros/name
 > 
 > RFC 1738 is explicit that the double slash at the beginning of the
 > path is allowed.
 > 
 > 
 > In RFC 2396 and RFC 2396bis, these appear to now be illegal. Is this
 > correct? Or am I misreading the BNF somehow? Are there any URI scheme
 > besides Prospero where this is likely to be an issue?

I'd agree with your reading of 1738 and 2396.

Another scheme that comes to mind is FTP.  RFC 1738 explicitly says in
3.2.2 that a slash that is part of a <cwd> element must be escaped.

Extrapolating, RFC 2396 implies that the original URL is not a valid
URI and should be rewritten as:

prospero://host.dom/%2Fpros/name

The introduction of 2396 has this disclaimer:

   This document updates and merges "Uniform Resource Locators"
   [RFC1738] and "Relative Uniform Resource Locators" [RFC1808] in order
   to define a single, generic syntax for all URI.  It excludes those
   portions of RFC 1738 that defined the specific syntax of individual
   URL schemes; those portions will be updated as separate documents, as
   will the process for registration of new URI schemes.

-- 
Pete Forman                -./\.-  Disclaimer: This post is originated
WesternGeco                  -./\.-   by myself and does not represent
pete.forman@w...    -./\.-   opinion of Schlumberger, Baker
http://petef.port5.com           -./\.-   Hughes or their divisions.

• References:
  • Prospero and other URLs with // in path
    • From: Elliotte Rusty Harold <elharo@m...>

• Prev by Date: RE: XML Technologies: Progress via Simplification or Complexification?
• Next by Date: RE: XML Technologies: Progress via Simplification or Complexification?
• Previous by thread: Prospero and other URLs with // in path
• Next by thread: Re: Early Draft Review: XQuery for Java (JSR 225)
• Index(es):
  • Date
  • Thread