Re: [PATCH setup 11/11] Use wininet for fetching URLs in direct (non-proxy) case (DO NOT APPLY)

[Jon Turney <jon.turney@dronecode.org.uk>]

On 03/05/2017 08:22, Brian Inglis wrote:
> On 2017-05-02 05:05, Jon Turney wrote:
>> On 02/05/2017 08:28, Ã…ke Rehnman wrote:
>>> On 2017-05-01 22:45, Jon Turney wrote:
>> I'm pretty sure I've done that in the past, so I think it already
>> works. The form of file: URL required might not be strictly correct,
>> though, (I think file:////server/pathname/ ?)
>> I can't see how to get a file:// URL for a local directory to parse
>> correctly, though.
>
> URLs are like http://host/path - file://host/path; if no host is given,
> localhost is assumed in http:///path and file:///path
>
> file:/// is the local root but some browsers accept just / e.g. lynx
> on Cygwin and Linux - useful to test this stuff, as GUI browsers look
> up URL history for completions.
> Most Windows browsers require the drive at the start of the path so
> should accept file:///d|/ (HTML originally allowed ":" only after the
> proto, and before the password and port in
> 	proto://[[[user][:pswd]@]host[:port]]/path
> so d| was required but that was relaxed in IE, and later other browsers
> followed), so likely file:///C:/, just C:, maybe C:/, rarely or never /.

Yes.  Unfortunately, none of this works correctly in setup at the moment.

Incorrect URLs of the form 'file:////server/pathname/' work in setup, 
but my attempts to construct something setup would use as a file URL for 
a local directory were unsuccessful.