> Markdown version of [/videos/697-brewing-tea-over-the-internet?t=305](https://www.wearedevelopers.com/videos/697-brewing-tea-over-the-internet?t=305). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Brewing Tea over the Internet

To mock HTTP's chaotic architectural bloat, engineers drafted a joke protocol for brewing coffee. Discover the hilarious history and real networking lessons behind the "418 I'm a teapot" error.

- **Speakers:** Imran Nazar
- **Event:** World Congress 2023
- **Published:** September 27, 2023
- **Duration:** 23:27
- **URL:** https://www.wearedevelopers.com/videos/697-brewing-tea-over-the-internet

## Summary

The evolution of HTTP reveals how an initially minimalistic protocol expanded, sometimes haphazardly, to accommodate the complex requirements of the modern internet. During the era of the HTTP 0.9 draft, the specification was incredibly rudimentary, relying entirely on a lone GET verb without structured error codes, which forced end-users to manually parse HTML to decipher whether a request succeeded. As developers eagerly added functionality, early file transfer protocols were bypassed in favor of bolting email MIME standards directly onto HTTP POST requests, essentially forcing early browsers and web servers to double as email clients. This rapid, uncontrolled extension permanently enshrined quirks into the specification, such as the ubiquitous misspelling of the referer header. To actively satirize these inappropriate extensions to HTTP, the engineering community began publishing joke RFCs like Hyper Text Coffee Pot Control Protocol, which brilliantly critiqued architectural bloat by introducing a BREW verb and the widely celebrated 418 I'm a teapot error code. Expanding HTCPCP to support tea appliances further demonstrates protocol flexibility by utilizing the 300 Multiple Choices status code to handle complex beverage selections natively. These humorous internet standards do more than provide comic relief; analyzing concepts like IP over Avian Carrier highlights fundamental networking realities around high bandwidth combined with extreme packet latency, while evaluating REST architecture verifies that mapping document operations to database records remains a thoroughly logical extension of Sir Tim Berners-Lee's original networking foundation.

**Keywords:** http protocol evolution, http 0.9 draft history, web standard extensions, post request attachments, mime type implementation, internet joke standard rfc, hyper text coffee pot control protocol, 418 teapot error code, rest architecture mapping, 300 multiple choices status, ip over avian carrier, network packet latency, evil bit firewall protocol, referer header misspelling, safe header implementation

## Chapters

1. **The history and evolution of early HTTP drafts** (00:03) — The initial text-based HTTP protocol lacked paths and error codes.
1. **Standardizing the HTTP protocol and adding response headers** (02:52) — New verbs, paths, and status codes transformed HTTP into a programmatic protocol.
1. **Reusing email software standards for HTTP file uploads** (05:05) — The inclusion of email MIME types enabled multipart form data and file attachments over HTTP.
1. **The coffee pot control protocol and brew verb** (08:43) — An April Fools internet standard formalized ridiculous extensions to HTTP network requests.
1. **The origin of the HTTP 418 teapot error** (12:21) — The introduction of the teapot error code became a beloved engineering community joke.
1. **Extending the coffee protocol for tea appliance hardware** (13:28) — The coffee protocol was eventually modified to support tea brewing with selection and rejection codes.
1. **REST principles and inappropriate HTTP response status codes** (15:28) — Using document verbs for database rows contrasts with returning success codes for internal errors.
1. **Reviewing other humorous internet engineering standard network RFCs** (17:02) — Joke standards mock concepts like firewall intention checking and extreme physical packet transport.
1. **Physical hardware implementations of the coffee appliance protocol** (19:07) — Hackathon projects have successfully built working appliances driven by the humorous protocol.
1. **Audience questions on avian carriers and binary HTTP** (20:40) — Discussions explore carrier pigeon packet loss mechanics and binary protocol formats.

## Related Moments

- [Representational state transfer and the adoption of HTTP verbs](https://www.wearedevelopers.com/videos/759-awful-apis-a-history-lesson-in-industry-mistakes-and-mishaps) (from "Awful APIs: A History Lesson in Industry Mistakes and Mishaps")
- [Core principles of the REST architectural style](https://www.wearedevelopers.com/videos/355-devouring-apis-with-python) (from "Devouring APIs with Python")
- [Questions on HTTP QUERY and AI standard timelines](https://www.wearedevelopers.com/videos/100014-what-s-new-in-web-2026-edition) (from "What’s New in Web? 2026 Edition")
- [Deprecating old email protocols and preserving niche online communities](https://www.wearedevelopers.com/videos/1814-wearedevelopers-live-markdown-liquid-and-checkouts) (from "WeAreDevelopers LIVE - Markdown, Liquid and Checkouts")
- [Historical evolution from remote procedure calls to modern protocols](https://www.wearedevelopers.com/videos/1195-the-great-api-debate-rest-graphql-or-grpc) (from "The Great API Debate: REST, GraphQL, or gRPC?")
- [Supporting modern network protocols in foundational libraries](https://www.wearedevelopers.com/videos/1796-don-t-insert-crazy-on-curl-and-ai-slop-daniel-stenberg) (from "Don’t Insert Crazy! On cURL and AI Slop - Daniel Stenberg")

## Related Articles

- [Dev Digest 126 - * yells at cloud](https://www.wearedevelopers.com/magazine/463-dev-digest-126-yells-at-cloud)
- [Dev Digest 139 - Soft and hard queries](https://www.wearedevelopers.com/magazine/487-dev-digest-139-soft-and-hard-queries)
- [Dev Digest 128 - Do not Google Monopoly](https://www.wearedevelopers.com/magazine/465-dev-digest-128-do-not-google-monopoly)
- [Dev Digest 123 - Easy as A, B, C1](https://www.wearedevelopers.com/magazine/459-dev-digest-123-easy-as-a-b-c1)

## Related Jobs

- [Senior Engineer, Infrastructure Platform](https://www.wearedevelopers.com/jobs/ext/328836-senior-engineer-infrastructure-platform) at **Intercom, Inc.**
- [Technical Support Engineer 2](https://www.wearedevelopers.com/jobs/ext/1911757-technical-support-engineer-2) at **Twilio**
- [Technical Support Engineer 2](https://www.wearedevelopers.com/jobs/ext/171621-technical-support-engineer-2) at **Twilio**
- [Senior Forward Deployed Engineer](https://www.wearedevelopers.com/jobs/ext/1915768-senior-forward-deployed-engineer) at **Intercom**
- [IT Systems Engineer](https://www.wearedevelopers.com/jobs/ext/25712-it-systems-engineer) at **Intercom, Inc.**
- [IT Systems Engineer](https://www.wearedevelopers.com/jobs/ext/185938-it-systems-engineer) at **Intercom**