Hypertext Transfer Protocol (HTTP) Status Code Registry -- Per [RFC2817] (last updated 2007-10-17) The HTTP Status Code Registry defines the name space for the Status-Code token in the Status line of an HTTP response. The initial values for this name space are those specified by: 1. Draft Standard for HTTP/1.1 2. Web Distributed Authoring and Versioning [defines 420-424] 3. WebDAV Advanced Collections (Work in Progress) [defines 425] 4. Section 6 [defines 426] Values to be added to this name space SHOULD be subject to review in the form of a standards track document within the IETF Applications Area. Any such document SHOULD be traceable through statuses of either 'Obsoletes' or 'Updates' to the Draft Standard for HTTP/1.1. HTTP Status Code Registry Value Description Reference ----- ---------------------------------- --------- 100 Continue [RFC2616] 101 Switching Protocols [RFC2616] 102 Processing [RFC2518] 200 OK [RFC2616] 201 Created [RFC2616] 202 Accepted [RFC2616] 203 Non-Authoritative Information [RFC2616] 204 No Content [RFC2616] 205 Reset Content [RFC2616] 206 Partial Content [RFC2616] 207 Multi-Status [RFC4918] 226 IM Used [RFC3229] 300 Multiple Choices [RFC2616] 301 Moved Permanently [RFC2616] 302 Found [RFC2616] 303 See Other [RFC2616] 304 Not Modified [RFC2616] 305 Use Proxy [RFC2616] 306 Reserved [RFC2616] 307 Temporary Redirect [RFC2616] 400 Bad Request [RFC2616] 401 Unauthorized [RFC2616] 402 Payment Required [RFC2616] 403 Forbidden [RFC2616] 404 Not Found [RFC2616] 405 Method Not Allowed [RFC2616] 406 Not Acceptable [RFC2616] 407 Proxy Authentication Required [RFC2616] 408 Request Timeout [RFC2616] 409 Conflict [RFC2616] 410 Gone [RFC2616] 411 Length Required [RFC2616] 412 Precondition Failed [RFC2616] 413 Request Entity Too Large [RFC2616] 414 Request-URI Too Long [RFC2616] 415 Unsupported Media Type [RFC2616] 416 Requested Range Not Satisfiable [RFC2616] 417 Expectation Failed [RFC2616] 422 Unprocessable Entity [RFC4918] 423 Locked [RFC4918] 424 Failed Dependency [RFC4918] 426 Upgrade Required [RFC2817] 500 Internal Server Error [RFC2616] 501 Not Implemented [RFC2616] 502 Bad Gateway [RFC2616] 503 Service Unavailable [RFC2616] 504 Gateway Timeout [RFC2616] 505 HTTP Version Not Supported [RFC2616] 506 Variant Also Negotiates (Experimental) [RFC2295] 507 Insufficient Storage [RFC4918] 510 Not Extended [RFC2774] Reference --------- [RFC2295] K. Holtman, A. Mutz, "Transparent Content Negotiation in HTTP", RFC2295, March 1998. [RFC2518] Y. Goland, E. Whitehead, A. Faizi, S. Carter, D. Jensen, "HTTP Extensions for Distributed Authoring -- WEBDAV", RFC 2518, February 1999. [RFC2616] R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, T. Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. [RFC2774] H. Nielsen, P. Leach, S. Lawrence, "An HTTP Extension Framework", RFC 2774, February 2000. [RFC2817] Khare, R., Lawrence, S., "Upgrading to TLS Within HTTP/1.1", RFC 2817, May 2000. [RFC3229] J. Mogul, B. Krishnamurthy, F. Douglis, A. Feldmann, Y. Goland, A. Hoff, and D. Hellerstein, "Delta encoding in HTTP", RFC 3229, January 2002. [RFC4918] L. Dusseault, "HTTP Extensions for Distributed Authoring - WebDAV", RFC 4918, June 2007. []