418 I'm a Teapot
4xx client error
An April Fools status defined in the HTCPCP spec for a coffee pot asked to brew tea, now used by sites for playful easter eggs.
Common causes
- An endpoint deliberately returns it as a joke.
- A tea-themed route exists next to real coffee routes.
- A framework maps the code from a custom exception.
How to fix it
- Keep a real body so the joke status still explains itself.
- Do not use 418 where a normal 4xx would be clearer in an API contract.
- Monitor it like any other status so real errors are not hidden.
What it means for redirects and SEO
A joke status still renders as a normal page, so it indexes fine but signals informality. Monitor it like a 200. Some link checkers do not recognise it in reports.