Why URLs Have Two Slashes: The Apollo Workstation Origin
This article explains the historical reason behind the double slash (//) in URLs, tracing it to Tim Berners-Lee's adoption of Apollo Domain workstation syntax in 1989, and clarifies how // marks the authority component in URIs, contrasting with schemes like mailto and data that omit it.
You type a URL like https://www.google.com every day, but have you ever wondered why there are two slashes after the colon? This article breaks down the URI syntax, reveals the surprising 1980s origin of the double slash, and shows why some URI schemes don't use it at all.
URI Structure and the Role of //
According to RFC 3986, a URI consists of a scheme, an authority, and a path. In https://www.example.com/path/to/page: https is the scheme (protocol). www.example.com is the host (authority). /path/to/page is the path.
The // is the delimiter that marks the start of the authority component — essentially a signpost telling the parser, "what follows is the server that will handle this request."
Historical Origin: Copied from Apollo Domain
Tim Berners-Lee designed the URL syntax in 1989 at CERN. The single slash for paths came directly from Unix file paths. However, the double slash was not his invention; he borrowed it from the Apollo Domain workstation, a high-end 1980s system whose OS could reference network files directly in paths using the syntax: //machine_name/path/to/file The leading // signaled "this is not a local directory, it's another machine." Berners-Lee later admitted, "I just copied Apollo." Thus http:// inherited those two slashes.
Schemes That Don't Need //
The double slash is not mandatory for all URIs. It only appears when a scheme needs to locate a remote server. Examples of schemes without //: mailto:[email protected] — email address is sufficient, no server lookup in the URI. tel:+8613800138000 — phone number triggers the dialer directly. data:text/html,<h1>Hello</h1> — the entire resource is embedded in the URI; no network request. javascript: — executes code in the browser (modern browsers block pasting such URLs for security).
In each case, the scheme itself carries all necessary information, so no authority delimiter is needed.
Special Cases: file:/// and Protocol-Relative URLs
The file: scheme uses three slashes: file:///Users/xxx/Desktop/test.html. The first two are the authority delimiter, but the authority is empty (local file), so the third slash begins the path. This yields the visually odd but syntactically correct triple slash.
Frontend developers may recall protocol-relative URLs like
<script src="//cdn.jquery.com/jquery.min.js"></script>. The leading // tells the browser to inherit the current page's scheme (HTTP or HTTPS). This was useful during the HTTP/HTTPS transition but is now rare since HTTPS is ubiquitous.
Modern Browsers Hide the Slashes
Today Chrome and Safari hide https:// in the address bar, showing only the domain. Berners-Lee once apologized that the two characters wasted paper and ink; the modern solution is not to remove them from the spec but to hide them in the UI.
The double slash is not a default part of every URI; it is a signal that lights up only when "I need to connect to a machine."
Understanding this history clarifies URI design and explains why some URLs look different from others.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
