Re: [whatwg/url] Allow ports in file URLs (#548)

I'm also curious why we prevent a username and password in a file URL when https://tools.ietf.org/html/rfc8089#appendix-E.1 clearly includes them.  I can easily imagine a use case when the host requires credentials, but that would add another place where a colon could be in a file URL, although not in the path.  Allowing a port would also allow a colon, but not in the path.  The comment in issue #97 says "that would require a lot more monkey-ing about with the UNC & drive-letter sniffing logic."  What would it take to do that "monkey-ing about" and make it only look in the path for drive letters?
FWIW, as of this morning this is the last url-constructor.html web platform test that is failing in WebKit.

-- 
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/548#issuecomment-703701608