Hi!

Well, unfortunately I don't remember the details. :) But I think the
case is that 2396 is the general RFC in effect for URIs and 1738 is the
RFC in effect for URLs using the "file" scheme. At least it says so at:
	http://www.iana.org/assignments/uri-schemes

Here is an excerpt from 1738:

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 btw, here is a posting on libcurl's list that shows that there is
indeed an issue:

	http://curl.haxx.se/mail/archive-2001-08/0021.html

Note that we are talking about *file URLs*. My memory is really bad but
when I dug into this I came to the conclusion that currently there is no
such thing as a relative file URL.

So what did I mean? :) Well, I think I meant that a *file URL* is "a
weird thing" that can't really be treated in practice based on the RFCs
for URIs. The tools do lots of "smart things" in order to handle a whole
range of false file URLs.

regards, Göran