Just so you can say you follow the standards :=) The RFC for Uniform Resource Locators (ftp://ftp.isi.edu/in-notes/rfc1738.txt) states the following concerning the file: scheme: <snip begin> 3.10 FILES 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>. For example, a VMS file DISK$USER:[MY.NOTES]NOTE123456.TXT might become <URL:file://vms.host.edu/disk$user/my/notes/note12345.txt> 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'. The file URL scheme is unusual in that it does not specify an Internet protocol or access method for such files; as such, its utility in network protocols between hosts is limited. <snip end> Thus you just need to check that if you are not using the host info - then there has to be 3 /'s and other wise it will be interpreted as a host on which it should find the file. How it does that is dependent on the system that parses and resolves the URL. Max R. Andersen ([EMAIL PROTECTED])
