Hubert Christiaen wrote: > An URL is composed of > - a protocol part ended with ':' ftp:' 'http:' or 'file:'
This is the URI scheme. It doesn't necessarily name a "protocol". > - an address of the server starting with '//' and ending in '/' > if the server is the localmachine, one can put 'localhost' or sometimes > also > just nothing. In this case you have for a file on your machine > already 'file:///' ! > - then follows the location on the server, which is a bit OS dependent ... The main point, in a case like this, is that the backslash (\) is not a valid URI character, nor is it the URI component separator for a hierarchical path. A valid file-scheme URL must use the forward slash (/). There's nothing OS-dependent about that; it's required by the URI specification. -- Michael Wojcik Micro Focus Rhetoric & Writing, Michigan State University
