- From: Mahmoud Hashemi <notifications@github.com>
- Date: Thu, 02 Feb 2017 22:52:33 -0800
- To: whatwg/url <url@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 3 February 2017 06:53:06 UTC
Talk about a quick response! This isn't so much about the protocol itself, it's actually very URL-intrinsic. So here's where this comes up. As you know, URLs with a scheme that uses a network location get a '//' whereas those without do not. `http://github.com` vs `mailto:mahmoud@hatnote.com`. If the standard is enforced strictly, and the scheme is treated as a whole, it's not possible to guess if a scheme implies the URL has a network location. So we don't know whether it should be `git+ftp://...` or `git+ftp:...`, despite the fact that you or I can clearly guess. A manifestation of this can be seen in Python's built-in URL support, here: https://hg.python.org/cpython/file/2.7/Lib/urlparse.py#l41 -- 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/230#issuecomment-277177423
Received on Friday, 3 February 2017 06:53:06 UTC