HTTP Status Codes in Use

This is a collection of HTTP Status Codes references by the IETF that are currently in use. Those range from informative HTTP/1.0 over the standard tracks up to experimental ones. I have collected it while working on an older #9297

All RFCs referenced in the IANA HTTP Status Code registry and related ones have been looked-up and tracked again: RFC 2295 (experimental); RFC 2518 (obsoleted); RFC 2616; RFC 2774 (experimental); RFC 2817; RFC 2818 (informational); RFC 3229; RFC 4918; RFC 5689; RFC 5785 and RFC 5842 (experimental).

Next to those, HTTP/1.0 as RFC 1945 (informational) has been looked-up again. It is a sort of subset of the standard HTTP/1.1 status codes from RFC 2616.

It has to be said that the IANA registry listing incl. the 102 status which I think is obsolete due to the properties of RFC 5842:

Note: the HTTP status code 102 (Processing) has been removed in this
specification; its IANA registration should continue to reference RFC
2518.

List of HTTP Status Codes

  1. Informational 1xx HTTP/1.0 (W3C); HTTP/1.1 (W3C)

  2. Successful 2xx HTTP/1.0 (W3C); HTTP/1.1 (W3C)

  3. 206 : Partial Content
  4. 207 : Multi-Status
  5. 208 : Already Reported
  6. 226 : IM Used
  7. 300 : Multiple Choices
  8. 301 : Moved Permanently
  9. 302 : Found
  10. 303 : See Other
  11. 304 : Not Modified
  12. 305 : Use Proxy
  13. 307 : Temporary Redirect
  14. 400 : Bad Request
  15. 401 : Unauthorized
  16. 402 : Payment Required
  17. 403 : Forbidden
  18. 404 : Not Found
  19. 405 : Method Not Allowed
  20. 406 : Not Acceptable
  21. 407 : Proxy Authentication Required
  22. 408 : Request Time-out
  23. 409 : Conflict
  24. 410 : Gone
  25. 411 : Length Required
  26. 412 : Precondition Failed
  27. 413 : Request Entity Too Large
  28. 414 : Request-URI Too Large
  29. 415 : Unsupported Media Type
  30. 416 : Requested range not satisfiable
  31. 417 : Expectation Failed
  32. 422 : Unprocessable Entity
  33. 423 : Locked
  34. 424 : Failed Dependency
  35. 426 : Upgrade Required
  36. 500 : Internal Server Error
  37. 501 : Not Implemented
  38. 502 : Bad Gateway
  39. 503 : Service Unavailable
  40. 504 : Gateway Time-out
  41. 505 : HTTP Version not supported
  42. 506 : Variant Also Negotiates
  43. 507 : Insufficient Storage
  44. 508 : Loop Detected
  45. 510 : Not Extended

Number of Status Codes by HTTP version

HTTP/1.0 – Total: 15

  1. [RFC 1945] 15 (informational)

HTTP/1.1 – Total: 51

  1. [RFC2295] 1
  2. [RFC 2518] 0 (obsoleted)
  3. [RFC 2616] 40
  4. [RFC 2774] 1 (experimental)
  5. [RFC 2817] 1
  6. [RFC 2818] 0 (informational)
  7. [RFC 3229] 1
  8. [RFC 4918] 5
  9. [RFC 5689] 0
  10. [RFC 5785] 0
  11. [RFC 5842 ] 2 (experimental)

Related Ticket is: #13940

This entry was posted in Hacking The Core, Pressed, Surviving the Internet and tagged , , , , , , , , , , , , , , , , , , . Bookmark the permalink.

One Response to HTTP Status Codes in Use

  1. Pingback: wordpress HTTP and header related tickets | hakre on wordpress

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s