418 I'm a teapot (RFC 2324, RFC 7168)

This code was defined in 1998 as one of the traditional IETF April Fools' jokes, in RFC 2324Hyper Text Coffee Pot Control Protocol, and is not expected to be implemented by actual HTTP servers. The RFC specifies this code should be returned by teapots requested to brew coffee.[53] This HTTP status is used as an Easter egg in some websites, including Google.com.[54][55]

Did you find this article useful?

  • 100 Continue

    The server has received the request headers and the client should proceed to send the request body...
  • 101 Switching Protocols

    The requester has asked the server to switch protocols and the server has agreed to do so....
  • 102 Processing

    A WebDAV request may contain many sub-requests involving file operations, requiring a long time to c...
  • 200 OK

    Standard response for successful HTTP requests....
  • 201 Created

    The request has been fulfilled, resulting in the creation of a new resource....