W3C home > Mailing lists > Public > uri@w3.org > May 2003

Re: Some clarification on file URLs

From: John Cowan <cowan@mercury.ccil.org>
Date: Mon, 19 May 2003 07:05:39 -0400
To: Israel Viente <israel_viente@il.vio.com>
Cc: uri@w3.org
Message-ID: <20030519110539.GL15637@ccil.org>

Israel Viente scripsit:

> 1. Can I describe the UNC path
> "\\file_server\share\file.txt"
> 
> by "file://file_server/share/file.txt" ?
> 
> 2. Is "file://10.213.123.23/c:/temp/file.txt" a valid file URL ?
> 
> 3. Are "file:///c:/temp" and file:///c/temp (without the ":") equivalent ?
> 
> 4. Is it right to say that the file URL "file:///outputFile" has meaning in Unix platform (/outputFile)
> but has no defined meaning in Windows or Macintosh platforms (since there is no single root disk) ?
> 
> 5. How should I describe Unix root directory : file:/// (3 "/") or file://// (4 "/") ?

The answers to all your questions are system- and even library-dependent,
as file: explicitly depends on the conventions of the local system
(except for using / as the hierarchical separator).  Most systems ignore
the host field, but the old libwww treated a host field other than
localhost as meaning "use FTP instead".  UNC support is certainly
possible; whether anyone does it is another question.

-- 
John Cowan  www.ccil.org/~cowan  www.reutershealth.com  jcowan@reutershealth.com
In might the Feanorians / that swore the unforgotten oath
brought war into Arvernien / with burning and with broken troth.
and Elwing from her fastness dim / then cast her in the waters wide,
but like a mew was swiftly borne, / uplifted o'er the roaring tide.
        --the Earendillinwe
Received on Monday, 19 May 2003 07:09:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 13 January 2011 12:15:31 GMT