On Sun, 2009-11-01 at 16:01 +0000, [email protected] wrote: > Author: chris_y > Date: Sun Nov 1 10:01:07 2009 > New Revision: 9656 > > URL: http://source.netsurf-browser.org?rev=9656&view=rev > Log: > Support file://(/)localhost/ as well as file://(/) > As NetSurf insists on adding a third slash after file://, it is not possible > to open > any local files which are in subdirectory "localhost" of the current > directory. > Workaround is to type the "localhost" part in something other than fully > lowercase. > In practice it is incredibly unlikely that even the workaround will need to > be used.
I don't understand the need for this. File URIs take the form: file://<hostname>/<path> However, the hostname may be completely omitted, and localhost inferred. The '/' between the hostname and the path may not be omitted, even if the hostname is. NetSurf does not support opening files on hosts that are not the local host. Additionally, it omits the hostname part, as it's unnecessary. Therefore, all file URIs in NetSurf are of the form: file:///<path> This is correct, per spec. The path component of a file: URI is a standard URI path. That is, it is a '/'-separated list of directories, with a trailing filename. Note: this is the case on all platforms, regardless of what the given platform's native path format is. Given the above, I don't understand what the issue you are encountering is. J.
