History of the Internet

Webvan Built for 8,000 Orders a Day. Its Warehouses Ran Below 40%.

The order button was small. The building behind it was roughly 350,000 square feet. Webvan's own annual report put the gap between those two objects in numbers: each distribution center was designed for 8,000 daily orders, while the centers were operating below 40% of their designed capacity.

DNS Record Kept Its Type. The Branch Name Changed Its Job.

The DNS Record Kept Its Type. The Branch Name Changed Its Job.

A TXT record can carry one service's instructions or another's. The DNS wire format will return both as TXT; it will not explain which application owns which meaning. For years, protocol authors put records under names beginning with an underscore to make a small private shelf beneath a domain. By 2019, so many shelves had been specified independently that the shelf names themselves needed a registry. RFC 8552 put a guard at the label closest to the DNS root: same record type, same global shelf name, one coordinated assignment.

IANA Stamped the Name “Special.” Your Resolver Still Had to Decide.

A domain name can look ordinary and require an extraordinary answer. Type a name ending in localhost and the address should loop back to the same machine. Ask for a name under invalid and the answer should be no such name. Ask about a private-address reverse zone and the answer may depend on the network you are standing in. In 2013, RFC 6761 put such names in one IANA register. It also made the register's central problem explicit: a label on a list cannot tell every application, resolver and operator how to behave.

Browser Counted the Port and Ignored the Path

The Browser Counted the Port and Ignored the Path

A web page needed a border. RFC 6454 drew it around scheme, host and port, leaving every path inside the same browser security unit.

@Handle Traveled; the Domain Kept the Address Book

The @Handle Traveled; the Domain Kept the Address Book

WebFinger let software turn a familiar account name into a useful link. The domain behind the name still answered the question—and controlled the map.

Sensor Was There. The Controller Had No Way to Find It.

The Sensor Was There. The Controller Had No Way to Find It.

A building controller knows it needs a light reading. Somewhere on the low-power network sits a sensor that can provide one. The controller still needs a path to the right resource, and nobody is standing by to click through a website. In August 2012, [RFC 6690](https://www.rfc-editor.org/rfc/rfc6690.html) gave constrained servers a small front desk: `/.well-known/core` returns links describing the resources they choose to expose. A controller can read the map, select a link and then ask the sensor itself.

Push Web Put Your Subscription on a Lease

The Push Web Put Your Subscription on a Lease

PubSubHubbub promised to stop feed readers knocking on every door. WebSub kept the fast delivery desk and gave each place in line an expiry time.

Canonical Tag Gave Webmasters a Vote, Not the Count

The Canonical Tag Gave Webmasters a Vote, Not the Count

A one-line promise to clean up duplicate URLs arrived in 2009. Its small print left the representative page in the hands of the search index.

HTTP/2 Wouldn’t Hand Over the Whole Connection. WebSocket Took One Stream.

An ordinary page is loading over HTTP/2. A chat window wants a WebSocket at the same time. The older WebSocket opening would ask the server to switch the entire connection away from HTTP, an awkward demand when that connection already carries several independent streams. [RFC 8441](https://www.rfc-editor.org/rfc/rfc8441.html), published in September 2018, gave the chat a smaller prize: after the server opts in, an extended CONNECT opens a tunnel on one stream. The page’s other requests keep moving beside it.

Script Was Fixed. AppCache Kept the Old App.

The Script Was Fixed. AppCache Kept the Old App.

A web developer could repair a file on the server while an offline reader kept the old application. The cache manifest decided when a complete new bundle arrived.

TLS 1.3 Wore a TLS 1.2 Name Tag. It Hid a Downgrade Alarm in Eight Bytes.

The newest version of a security protocol introduced itself with an old version number. A TLS 1.3 handshake left `0x0303`, the number for TLS 1.2, in a field that earlier software expected to read. The actual version traveled in an extension. That apparent costume was part of the price of crossing networks filled with devices that inspected handshakes they did not own. [RFC 8446](https://www.rfc-editor.org/rfc/rfc8446.html) also placed an alarm in a server's random bytes: if a capable server settled for an older version, the client could see the sign and refuse the connection.

Browser Fit on a Cheap Phone. The Work Went to Opera's Server.

The Browser Fit on a Cheap Phone. The Work Went to Opera's Server.

In 2005 a small Java client brought web pages to modest phones because Opera prepared them elsewhere. The carrier saw a data business in the same design.

Page Said SAMEORIGIN. The Browser Missed the Frame in the Middle.

The Page Said SAMEORIGIN. The Browser Missed the Frame in the Middle.

A protected page and the top page shared an origin. The untrusted page between them was the problem that a shallow browser check could miss.

Spam Filter Opened a Link. The Mailing List Lost a Reader.

The Spam Filter Opened a Link. The Mailing List Lost a Reader.

An email filter opens a link to inspect it. The mailing list treats the visit as an instruction to remove its reader. No person asked to leave; a machine merely looked. That was the trap behind a convenient feature of email, and it drove a precise repair in January 2017. [RFC 8058](https://www.rfc-editor.org/rfc/rfc8058.html) separated the advertised exit from the act of taking it: a signed signal in the message, an explicit choice by the reader, and an HTTPS POST that actually changes the list.

Chrome Put the Web’s Service Switchboard in Its Store. Then It Switched It Off.

A site could ask the browser to find a photo editor. Chrome tested the idea with a store-only service gate, disabled it months later, and W3C stopped the standard.

Markdown Got One MIME Type. Its Readers Kept Disagreeing.

A writer sends a Markdown file. One reader sees a table; another sees pipes and dashes. Both received the same bytes. In March 2016, an Internet RFC gave that file a proper media type, `text/markdown`, and a place to name its dialect. It left the decisive act with the receiving software. A label could travel across systems; the rules for turning punctuation into a page still had to be understood at the other end.

Cookie Banner Took a Job Browsers Couldn’t Do

The Cookie Banner Took a Job Browsers Couldn’t Do

A 2009 European rule needed consent. Britain’s 2012 regulator found browser settings too blunt, and the courts later rejected a checkbox that answered for the user.

Microsoft’s Browser Ballot Missed 15.3 Million People. The Fix Was Half a Page.

Brussels required a browser choice screen on eligible Windows PCs. A Windows Update rule failed to recognize machines with Service Pack 1, and the compliance reports kept saying the package had gone out.

Server Had 500. The Cache Returned 200—and an Old Page.

The Server Had 500. The Cache Returned 200—and an Old Page.

The origin fails, yet the reader receives a successful response from a cache. On another day the origin merely takes time to check a page, and the cache sends its older copy before that check finishes. In 2010, RFC 5861 gave these two bargains separate names and separate time limits. Speed and availability rose because the origin let its intermediary serve an answer whose age could be measured. The reader paid with a delay in seeing change.

Google Talk Welcomed Other Clients. Other Servers Had to Wait.

A protocol badge on the launch day did not yet make a messaging network open. Google Talk first let independent programs enter its service; months later it opened a route between service providers.