> -----Original Message-----
> From: Michael Wood [mailto:mwood@its.uct.ac.za]
> On Wed, Oct 17, 2001 at 04:12:51AM -0700, Greg Stein wrote:
> > On Thu, Oct 11, 2001 at 05:28:48PM +0200, Michael Wood wrote:
> > >...
> > > I don't think file://d:/blah is a valid URL, so you might try
> >
> > Yes, it is a valid URL. Consider http://host:port/path ...
>
> That's completely different, and I suspect it's supposed to be
> http://host[:port]/blah, in which case http://host:/blah would
> be invalid (I haven't checked the relevant RFC, though.)
>
> Also, file:///blah is supposed to be equivalent to
> file://localhost/blah AFAIK.
>
> "d" is not a hostname, so how could file://d:/blah be valid?
> And d: is not a host:port either.
[snip]
Sounds about right...
>From RFC 1738:
"The file URL scheme is used to designate files accessible on a
particular host computer. This scheme, unlike most other URL schemes,
does not designate a resource that is universally accessible over the
Internet.
A file URL takes the form:
file://<host>/<path>
where <host> is the fully qualified domain name of the system on which
the <path> is accessible, and <path> is a hierarchical directory path
of the form <directory>/<directory>/.../<name>."
and then:
"As a special case, <host> can be the string "localhost" or the empty
string; this is interpreted as `the machine from which the URL is
being interpreted'."
So according to the RFC, the correct form should be
file://localhost/path/to/file with or without the localhost bit.
Reserved chars in the /path/to/file have to be escaped so you'd escape
out colons using the %xx syntax giving you file:///d%7c/path/to/file.
Personally I hate the pipe usage in netscape.
Marcus
--
Marcus Williams - http://www.onq2.com
Quintic Ltd, 39 Newnham Rd, Cambridge, CB3 9EY
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:44 2006