ronutz
← All vendors

Vendor lineage

HTTP & Gopher - the web's protocol and the rival it eclipsed

Two futures shipped in 1991; one spring of licensing decided between them - CERN gave the web away, Minnesota asked for money.

Gopher was the better-organized system and for two years it was winning. Then, weeks apart in 1993, Minnesota announced server fees and CERN declared the web royalty-free forever - the cleanest natural experiment in protocol economics ever run. HTTP went on to replace its own transport twice without breaking a URL.

The profile covers the 1989 CERN proposal and HTTP/0.9, Gopher's rise and Veronica, the spring-1993 licensing fork, Mosaic, the Host header, REST, and the HTTP/2-to-HTTP/3-over-QUIC arc this site's WAF material continues.

Founding stories

1989

HTTP and the World Wide Web

CERN, Geneva, Switzerland · Founders: Tim Berners-Lee, Robert Cailliau (co-author of the 1990 proposal)

In March 1989 Tim Berners-Lee circulated a memo at CERN proposing a hypertext system for keeping track of the laboratory's information; his manager Mike Sendall wrote 'vague, but exciting' in the margin and let him build it. By Christmas 1990 a NeXT workstation was running the first web server and the first browser, speaking HTTP/0.9 - a protocol so small it was one line: GET, a path, a document back, connection closed. The project was announced to the world on the alt.hypertext newsgroup on August 6, 1991. The web's founding insight was radical simplicity: URLs, HTML, and HTTP were each minimal enough to reimplement in a weekend - which is exactly what a planet of programmers proceeded to do.

1991

Gopher

University of Minnesota, Minneapolis · Founders: Mark P. McCahill, Farhad Anklesaria, Paul Lindner, Daniel Torrey, Bob Alberti

Weeks before the web's announcement, the University of Minnesota released Gopher - a campus information system organized as menus rather than hypertext, light enough for the text terminals and modems of 1991, and named for the school's mascot. For two years it looked like the future: gopherspace grew explosively, clients existed for every platform, and with Veronica in 1992 it had real search before the web had any. Gopher was, by most practical measures of the moment, the better-organized system - which is what makes what happened next the industry's most-cited lesson.

The timeline

  1. Two futures ship

    Gopher (spring, Minnesota) and the web (August 6 announcement, CERN) arrive months apart. Gopher's menus are instantly practical on the terminals people actually have; the web's hypertext is harder to see the point of - until screens, and then browsers, catch up.

    alt.hypertext announcement, August 6, 1991.

  2. Veronica

    Gopherspace gets a search engine - built at the University of Nevada, Reno - before the web has anything comparable; Jughead follows in 1993. For a moment, the menu world is the searchable one.

  3. Minnesota asks for money

    In the spring, the university announces licensing fees for commercial use of the Gopher server. Nothing about the protocol changes - but the community's chill is immediate, famous, and terminal. Adoption decisions being made that season quietly flip.

    University of Minnesota licensing announcement, spring 1993 - among the most-documented licensing decisions in internet history.

  4. CERN gives the web away

    April 30, 1993: CERN places the web's technology royalty-free into the public domain - anyone may build on it, forever, for nothing. Paired with Minnesota's move weeks earlier, it is the cleanest natural experiment in protocol economics ever run; the results arrived within eighteen months.

    CERN public-domain declaration, April 30, 1993 (document preserved by CERN).

  5. Mosaic makes it visual

    NCSA's browser puts images inline with text and installs in minutes - the web stops being an idea and becomes a place (that story is told in this encyclopedia's NCSA profile). Gopher's clean menus suddenly look like a directory listing next to a magazine.

  6. The crossing

    Web traffic passes Gopher on the NSFNET backbone during 1994-95 and never looks back; Netscape ships, SSL brings HTTPS, and commercial gopherspace plateaus into a long, quiet fade.

  7. HTTP grows up

    HTTP/1.0 (RFC 1945, 1996) formalizes what everyone was doing; HTTP/1.1 (RFC 2068 in 1997, refined as RFC 2616 in 1999) adds persistent connections, chunked transfer, and the Host header - the single header that made name-based virtual hosting, and thus affordable mass web hosting, economically possible. Roy Fielding's 2000 dissertation names the architectural style: REST.

    RFC 1945 (1996), RFC 2068 (1997), RFC 2616 (1999); Fielding dissertation (2000).

  8. Gopher's GPL epilogue

    The University of Minnesota relicenses Gopher under the GPL - gracious, correct, and seven years too late. A small gopherspace persists to this day, maintained by people who remember.

  9. HTTP/2

    RFC 7540, grown from Google's SPDY: binary framing, multiplexing, header compression - the first wire-format break in the protocol's history, carrying the same request semantics underneath.

    RFC 7540, May 2015.

  10. HTTP/3 over QUIC

    RFC 9114 over RFC 9000: the transport itself is replaced - UDP-based QUIC with TLS built in - while the semantics above survive intact. The lineage this site's WAF-over-QUIC material picks up in the present tense.

    RFC 9000 (2021) / RFC 9114 (2022).

Flagship products and solutions

  • HTTP/0.9 through HTTP/3From a one-line GET to a multiplexed, encrypted, UDP-transported protocol - four transport generations under one set of request semantics, which is why a 1990s URL can still resolve.
  • URLs, HTML, and the royalty-free webThe trio's openness was the product: minimal specifications, free forever by declaration, implementable by anyone in days.
  • Gopher and VeronicaThe menu-structured information space and its search engine - the best pre-web system, and the standing proof that better-organized is not the same thing as winning.

Key innovations

  • Radical simplicity as strategyHTTP/0.9 could be implemented in an afternoon, and that low floor recruited the largest implementer base in protocol history. Complexity came later, after ubiquity - the order matters.
  • The Host headerOne HTTP/1.1 field let a single IP address serve a thousand names - arguably the most commercially consequential header ever shipped, and the quiet foundation of the shared-hosting economy.
  • Licensing as fateSpring 1993, one decision each way: Minnesota asked for fees, CERN declared the web free forever. Every open-source strategy debate since has cited the outcome, usually within the first five minutes.

Main markets

Everything, eventually: publishing, commerce, software distribution, and then applications themselves - the progressive web app this site ships over HTTPS included. Gopher survives as a small, affectionately maintained hobbyist space.

Analyst standing

  • Gopher did not lose on technology - it lost on governance. The generalized lesson has held for three decades: when the prize is a network effect, open and unencumbered beats organized and owned.
  • HTTP is the rare protocol that replatformed its own transport twice (TCP text to binary framing to QUIC) without breaking its semantics - a masterclass in evolving the wire while honoring the contract.
  • For this site the pairing is load-bearing: HTTP is the substrate of every tool here, and the QUIC chapter is current, working material - see the WAF-over-QUIC article in Learn.