HTTP 418 is a reserved status code. Its “I’m a teapot” meaning comes from RFC 2324, a 1998 April Fools’ specification about brewing coffee. The current HTTP specification, RFC 9110, lists it as unused.
Tanımlandığı yer RFC 9110 §15.5.19 — 418 (Unused) · MDN referansı · RFC 2324 §2.3.2 — Hiper Metin Kahve Makinesi Kontrol Protokolü
RFC 9110 reserves 418 as unused. The teapot phrase comes from RFC 2324 §2.3.2, a 1998 April Fools’ specification.
curl -i https://funapi.dev/api/coffee/v1/teapot
The Coffee API returns 418 with an error message and an RFC 2324 reference. The hosted response also includes a requestId that varies by request.
{
"error": "I'm a teapot",
"message": "The requested entity body is short and stout. Tip me over and pour me out.",
"rfc": "RFC 2324"
}
Run the Coffee API teapot example
If you encounter a 418 from a live service, check that service’s documentation or proxy configuration. RFC 9110 gives the reserved code no standard application meaning.
Return 418 deliberately to check that your client, proxy and logs preserve an unexpected 4xx status. Assert the numeric status and inspect the JSON body.
Treat a deliberate 418 as a client error and keep the numeric status in logs. Use it to test your generic 4xx handling, including whether the response body remains available to the caller.
Bu oyun alanında 2 uç nokta 418 ile yanıt veriyor. Hepsi ücretsizdir, kayıt gerektirmez ve tarayıcıdan ya da curl ile çağrılabilir.
GET https://funapi.dev/api/coffee/v1/teapot — Try to brew coffee in a teapot (Coffee Shop API) Bu uç noktayı aç ve çalıştırGET https://funapi.dev/api/faults/v1/status/{code} — Return any status code on demand (200–599) (Fault Injection API) Bu uç noktayı aç ve çalıştırTüm HTTP durum kodları · 55 mock REST API’nin tamamı · Başlangıç rehberi
Son güncelleme