HTTP Status Code
In the server response message, the first line is the status line. Here's a example:
HTTP/1.1 200 OK
It has 3 parts: (1) the HTTP version. (2) the status code. (3) Human readable representation of the status code.
The status code has 3 digits. Its meaning is grouped into categories by the first digit:
- 1xx (Informational)
- The request was received, continuing process
- 2xx (Successful)
- The request was successfully received, understood, and accepted
- 3xx (Redirection)
- Further action needs to be taken in order to complete the request
- 4xx (Client Error)
- The request contains bad syntax or cannot be fulfilled
- 5xx (Server Error)
- The server failed to fulfill an apparently valid request
Here's a full list. Those with a 🌟 sign are most frequently used.
- 100
- Continue
- 101
- Switching Protocols
- 200
- 🌟 OK
- 201
- Created
- 202
- Accepted
- 203
- Non-Authoritative Information
- 204
- No Content
- 205
- Reset Content
- 206
- Partial Content
- 300
- Multiple Choices
- 301
- 🌟 Moved Permanently
- 302
- Found
- 303
- See Other
- 304
- Not Modified
- 305
- Use Proxy
- 307
- Temporary Redirect
- 400
- Bad Request
- 401
- Unauthorized
- 402
- Payment Required
- 403
- 🌟 Forbidden
- 404
- 🌟 Not Found
- 405
- Method Not Allowed
- 406
- Not Acceptable
- 407
- Proxy Authentication Required
- 408
- Request Timeout
- 409
- Conflict
- 410
- Gone
- 411
- Length Required
- 412
- Precondition Failed
- 413
- Payload Too Large
- 414
- URI Too Long
- 415
- Unsupported Media Type
- 416
- Range Not Satisfiable
- 417
- Expectation Failed
- 426
- Upgrade Required
- 500
- Internal Server Error
- 501
- Not Implemented
- 502
- Bad Gateway
- 503
- Service Unavailable
- 504
- Gateway Timeout
- 505
- HTTP Version Not Supported
For detail of all status code, see: [RFC 7231 HTTP/1.1: Semantics and Content By IETF. At https://tools.ietf.org/html/rfc7231 , accessed on 2016-04-02 ]