HTTP 418

Simulating HTTP status codes


200 OK

Standard response for successful HTTP requests.

201 Created

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

202 Accepted

The request has been accepted for processing, but the processing has not been completed. The request might or might not be eventually acted upon, and may be disallowed when processing occurs.

203 Non-Authoritative Information

The server is a transforming proxy (e.g. a Web accelerator) that received a 200 OK from its origin, but is returning a modified version of the origin's response

204 No Content

The server successfully processed the request and is not returning any content.

Status codes 205, 206, 207, 208 and 226 are not Supported by HTTP 418.


301 Moved Permanently

This and all future requests should be directed to the given URL.

302 Found


303 See Other

The response to the request can be found under another URL using a GET method.

304 Not Modified

Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-None-Match. HTTP 418 will alway return 304 Not Modified.

307 Temporary Redirect

The request should be repeated with another URL; however, future requests should still use the original URL.

308 Permanent Redirect

The request and all future requests should be repeated using another URL. 307 and 308 parallel the behaviours of 302 and 301, but do not allow the HTTP method to change.

Status codes 300, 305 and 306 are not Supported by HTTP 418.


400 Bad Request

The server cannot or will not process the request due to an apparent client error.

401 Unauthorized

Similar to 403 Forbidden, but specifically for use when authentication is possible but has failed or not yet been provided.

403 Forbidden

The request was a valid request, but the server is refusing to respond to it.

404 Not Found

The requested resource could not be found but may be available in the future.

405 Method Not Allowed

A request method is not supported for the requested resource.

406 Not Acceptable


408 Request Timeout

The server timed out waiting for the request.

409 Conflict

Indicates that the request could not be processed because of conflict in the request.

410 Gone

Indicates that the resource requested is no longer available and will not be available again.

411 Length Required

The request did not specify the length of its content, which is required by the requested resource.

412 Precondition Failed

The server does not meet one of the preconditions that the requester put on the request.

412 Payload Too Large

The request is larger than the server is willing or able to process.

414 URI Too Long

The URI provided was too long for the server to process. Often the result of too much data being encoded as a query-string of a GET request.

415 Unsupported Media Type

The request entity has a media type which the server or resource does not support

418 I'm a teapot

This code was defined in 1998 as one of the traditional IETF April Fools' jokes, in RFC 2324, Hyper Text Coffee Pot Control Protocol or HTCPCP.

429 Too Many Request

The user has sent too many requests in a given amount of time.

431 Request Header Fields Too Large

The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large.

451 Unavailable For Legal Reasons

A server operator has received a legal demand to deny access to a resource.

Status codes 407, 416, 417, 421, 422, 423, 424, 426 and 428 are not Supported by HTTP 418.


500 Internal Server Error

A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.

501 Not Implemented

The server either does not recognize the request method, or it lacks the ability to fulfill the request.

502 Bad Gateway

The server was acting as a gateway or proxy and received an invalid response from the upstream server.

503 Service Unavailable

The server is currently unavailable (because it is overloaded or down for maintenance).

504 Gateway Timeout

The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.

505 HTTP Version Not Supported

The server does not support the HTTP protocol version used in the request.

Status codes 506, 507, 508, 510 and 511 are not Supported by HTTP 418.