Technically, not all of them do; " :" is the common prefix, and everything else depends on the URL type. See: http://www.ietf.org/rfc/rfc1738.txt In particular, section 3.1, 'The scheme specific data start with a double slash "//" to indicate that it complies with the common Internet scheme syntax.'. So it is used by URLs that require any of this information: "// : @ : / ".
Ask HN: Why does a url use ://?
11–20 of 26 posts
Re: Ask HN: Why does a url use ://?
#12Re: Ask HN: Why does a url use ://?
#13Tim Berners Lee, the creator of the Web and of URLs, wrote some time ago that he regretted the double slash in URLs, saying that one would suffice.
http:/com/ycombinator/news/item?id=796434
Re: Ask HN: Why does a url use ://?
#14Re: Ask HN: Why does a url use ://?
#15Note that a url like //www.example.com will use the context's protocol, which means an img src="//www.example.com" will use http or https depending on which the page was loaded in. Very handy!
Re: Ask HN: Why does a url use ://?
#16Note that a url like //www.example.com will use the context's protocol, which means an img src="//www.example.com" will use http or https depending on which the page was loaded in. Very handy!
[deleted]
Re: Ask HN: Why does a url use ://?
#17Re: Ask HN: Why does a url use ://?
#18Tim Berners Lee, the creator of the Web and of URLs, wrote some time ago that he regretted the double slash in URLs, saying that one would suffice.
It went a little further than that, I think the scheme would have been: http:/com/ycombinator/news/item?id=796434
Re: Ask HN: Why does a url use ://?
#19Earlier quoted context omitted.
It went a little further than that, I think the scheme would have been: http:/com/ycombinator/news/item?id=796434
And that would have been awesome.
http:/com/test/www/someresource
and
http:/uk/co/test/www/someresource
Would have both been valid resources but it would be harder than now to figure out where the machine boundary is located.
You can't go by 'count' (because of subdomains) and you can't go by www either.
I think if they would have gone that route for practical reasons the // would have been 'reinvented', and it would probably be placed like this:
http:/com/ycombinator/news//some/path/resource.html
I'm not sure what the implications for phishing, certificates and humans interpreting URLs would have been in that situation either, but I know that I find it convenient to be able to fish the 'hostpart' out of a URL without further knowledge on my side.
Re: Ask HN: Why does a url use ://?
#20Earlier quoted context omitted.
And that would have been awesome.
Yes, but there would be a couple of problems as well, specifically the DNS would need some major revamping. The DNS was already operational long before the web came along and it already used the '.' notation. http:/com/test/www/someresource and http:/uk/co/test/www/someresource Would have both been valid resources but it would be harder than now to figure out where the machine boundary is located. You can't go by 'co…
rwj@uk.ac.dl.cxa
In fact the first "domain names" I used were things like "lancs.pdsoft" but I think those were X.25 names, and the less said about X.25 the better.
At some point around '91 or '92 JANET reversed all the domain names to bring it into line with IETF standards. This caused some confusion with names beginning "cs." which could either be the Computer Science dept of some UK unversity, or a domain in the old Czechoslovakia.