HTTP 1.1 Status Codes

• 200 OK—The Web Web Server processed the request.
• 201 Created—The Web Web Server created a new URI, specified in a Location header.
• 202 Accepted—Accepted for processing, but has not completed processing.
• 203 The meta information in the entity-header is not the definitive set as available from the origin Web Web Server.
• 204 No Content— Action is complete, but no information needs to be sent back.
• 205 Reset Content—The client should reset the current document.
• 206 Partial Content—The Web Web Server has fulfilled the partial GET request for the item.
• 300 Multiple Choices—The requested item corresponds to a set of documents.
• 301 Moved Permanently—The requested item does not exist on the Web Web Server.
• 302 Moved Temporarily—The requested item has temporarily moved.
• 303 See Other—The item is at a different location indicated by theheader, and the client should use the GET method to retrieve it.
• 304 Not Modified—The Web Web Server uses this code to respond to the If- Modified-Since request header.
• 305 Use Proxy—The client should use a proxy, specified by the Location header.
• 307 Temporary Redirect—The item is temporarily redirected to a different location.
• 400 Bad Request—The Web Web Server detected a syntax error in the client request.
• 401 Unauthorized—The request requires user authentication.
• 402 Payment Required—This code is not in use.
• 403 Forbidden—Access to item is forbidden.
• 404 Not Found—The document does not exist on the Server.
• 405 Method Not Allowed—The method used by the client is unacceptable.
• 406 Not Acceptable—The item is not available in a format that the client can accept.
• 407 Proxy Authentication Required—Unauthorized access request to a proxy Web Server.
• 408 Request Time-Out—The client has failed to complete its request within the timeout period.
• 409 Conflict—The client request conflicts with another request.
• 410 Gone—The requested item is permanently gone from the Web Server.
• 412 Precondition Failed—Web Server uses this code to indicate that one or more of the conditions specified in these headers is false.
• 413 Request Entity Too Large—The Web Server refuses to process the request because of a large message body.
• 414 Request-URI Too Long—The Web Server refuses to process the request because the specified URI is too long.
• 415 Unsupported Media Type—The Web Server refuses to process the request because it does not support the message body’s format.
• 417 Expectation Failed—The Web Server failed to meet the requirements of the Expect Request header.
• 500 Internal Web Server Error—A Web Server setting has caused an error.
• 501 Not Implemented—The Web Server does not support the functionality required.
• 502 Bad Gateway—The Web Server encountered an invalid response from an upstream Web Server or proxy.
• 503 Service Unavailable—The service is temporarily unavailable.
• 504 Gateway Time-Out—The gateway or proxy has timed out.
• 505 HTTP Version Not Supported—The version of HTTP used by client is not supported.