Is HTTP 418 I'm a teapot a real status code?
It comes from RFC 2324, the Hyper Text Coffee Pot Control Protocol, an April Fools' joke. It is not part of the HTTP standard, yet it is widely recognised and some servers return it deliberately. It has been defended against removal from libraries by developers who like the joke.
Answered in
The Strange HTTP Status Codes: 451, 418, 420, 218 and 530, and What They TeachFive odd status codes, which are standard, which are jokes and which are vendor inventions, and why custom codes are a trap for client code.
Read the full analysisOther questions this article answers
More development best practices questions
- What is the primary security vulnerability of storing JWTs in localStorage?
- How do server-side sessions scale horizontally across multiple instances?
- Why is immediate revocation nearly impossible with stateless JWTs?
- What is the recommended modern authentication architecture for SaaS apps?
- What is the N+1 query problem in GraphQL and how is it fixed?
- How does GraphQL Federation allow multiple backend teams to maintain one API?
- Why is caching harder in GraphQL than in traditional REST APIs?
- When should an engineering team prefer REST or gRPC over GraphQL?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the Development Best Practices beat.