4xx Client Error

HTTP 418 I'm a Teapot

This code was defined in 1998 as an April Fools' joke in RFC 2324, Hyper Text Coffee Pot Control Protocol. It is not expected to be implemented by actual HTTP servers, but it has become a beloved Easter egg.

Common Causes

  • Easter egg response from a server with a sense of humor
  • API returning a joke status for fun endpoints
  • Intentional use as a non-standard refusal response

How to Fix

  1. 1Enjoy the joke — this is an Easter egg, not a real error
  2. 2If unexpected, the server may be using it as a custom refusal
  3. 3Check if the server has a /coffee endpoint for fun

Example

HTTP 418 I'm a Teapot
GET /coffee HTTP/1.1

→ 418 I'm a Teapot
→ "I can't brew coffee, I'm a teapot!"

Related Client Error Codes

400

Bad Request

401

Unauthorized

402

Payment Required

403

Forbidden

404

Not Found

405

Method Not Allowed

406

Not Acceptable

407

Proxy Authentication Required

408

Request Timeout

409

Conflict

410

Gone

411

Length Required

412

Precondition Failed

413

Content Too Large

414

URI Too Long

415

Unsupported Media Type

416

Range Not Satisfiable

417

Expectation Failed

421

Misdirected Request

422

Unprocessable Content

423

Locked

424

Failed Dependency

425

Too Early

426

Upgrade Required

428

Precondition Required

429

Too Many Requests

431

Request Header Fields Too Large

451

Unavailable For Legal Reasons