Re: [whatwg/url] Empty or null host when scheme is "file:"? (#258)

It makes sense to use an empty string (also used in RFC 3986). But I don't think https://url.spec.whatwg.org/#scheme-relative-file-url-string must be changed, because second item allows empty host, i.e.:
> must be "//", followed by ... a path-absolute-URL string.

I think must be changed URL's host definition https://url.spec.whatwg.org/#concept-host (or maybe https://url.spec.whatwg.org/#concept-url-host). Currently this definition allows empty host but only as opaque host, but opaque host is for non-special URLs (see note at https://url.spec.whatwg.org/#opaque-host). So changed definition:
- A <b>host</b> is a domain, an IPv4 address, an IPv6 address, <del>or</del> an opaque host, <ins>or an empty host</ins>. Typically a host serves as a network address, but it is sometimes used as opaque identifier in URLs where a network address is not necessary.

A term <b>empty host</b> can be used for non-special and file URL's; then empty string (zero URL units) can be excluded from opaque host definition https://url.spec.whatwg.org/#valid-opaque-host-string  - so opaque host means not empty.

What do you think about such changes?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/258#issuecomment-282224426