418 I'm a teapot

4×× Client Error
418 I'm a teapot

Any attempt to brew coffee with a teapot should result in the error code "418 I'm a teapot". The resulting entity body MAY be short and stout.

    Source: RFC2324 Section 2.3.2

418 Code References

Go HTTP Status Constant http.StatusTeapot

Symfony HTTP Status Constant Response::HTTP_I_AM_A_TEAPOT
at
Labels:

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)
  • 416 Requested Range Not Satisfiable
    4×× Client Error 416 Requested Range Not Satisfiable None of the ranges in the request's Range header field1 overlap the current ext...
  • 511 Network Authentication Required
    5×× Server Error 511 Network Authentication Required The client needs to authenticate to gain network access. The response representat...
  • 599 Network Connect Timeout Error
    5×× Server Error 599 Network Connect Timeout Error This status code is not specified in any RFCs, but is used by some HTTP proxies to si...
  • 510 Not Extended
    5×× Server Error 510 Not Extended The policy for accessing the resource has not been met in the request. The server should send back all...
  • 200 OK
    The request has succeeded. The payload sent in a 200 response depends on the request method. For the methods defined by this specificatio...
  • 505 HTTP Version Not Supported
    5×× Server Error 505 HTTP Version Not Supported The server does not support, or refuses to support, the major version of HTTP that was u...
  • 429 Too Many Requests
    4×× Client Error 429 Too Many Requests The user has sent too many requests in a given amount of time ("rate limiting"). The ...
  • 506 Variant Also Negotiates
    5×× Server Error 506 Variant Also Negotiates The server has an internal configuration error: the chosen variant resource is configured t...
  • 508 Loop Detected
    5×× Server Error 508 Loop Detected The server terminated an operation because it encountered an infinite loop while processing a request...
  • 301 Moved Permanently
    The target resource has been assigned a new permanent URI and any future references to this resource ought to use one of the enclosed URIs....