The History of the URL: Path, Fragment, Query, and Auth

Re:The History of the URL: Path, Fragment, Query, and Auth by RockyMcNuts on Monday July 18, 2016 @05:35PM (#12118186)

I always suspected there must have been 2 archaic null tokens between the :// of http://...

If it was a design choice to use a 3-character separator instead of a single character, seems an odd choice.

[ Parent | on HN ]

Re:The History of the URL: Path, Fragment, Query, and Auth by DougBTX on Monday July 18, 2016 @05:53PM (#12118270)

https://www.ietf.org/rfc/rfc1738.txt may shed some light on this. It describes the ":" as the separator, while the // is a scheme-specific prefix, like a super-powered path separator.

More here: https://www.w3.org/People/Berners-Lee/FAQ.html#etc

[ Parent | on HN ]

Re:The History of the URL: Path, Fragment, Query, and Auth by pbhjpbhj on Monday July 18, 2016 @06:50PM (#12118475)

Well, it does allow references to //example.com to cover both http and https schemes.

[ Parent | on HN ]

Re:The History of the URL: Path, Fragment, Query, and Auth by zackbloom on Monday July 18, 2016 @07:00PM (#12118503)

It's discussed a bit in the first portion of this series: https://eager.io/blog/the-history-of-the-url-domain-and-prot...

[ Parent | on HN ]