Home >>HTTP Tutorial >HTTP Status Codes
HTTP Status Codes
HTTP Status Codes
In a server response, the Status-Code element is a 3-digit integer where the first digit of the Status-Code defines the response class and the last two digits have no categorising role. There are 5 First Digit values:
| Sr No | Code and Description |
|---|---|
| 1. | 1xx: Informational This means that the request was received, and the process continues. |
| 2. | 2xx: Success It means that the action was taken, understood and accepted with success. |
| 3. | 3xx: Redirection This means further action to complete the request must be taken. |
| 4. | 4xx: Client Error It means that the request contains incorrect syntax or cannot be complied with. |
| 5. | 5xx: Server Error It means that the server failed to respond to an obviously valid request. |
HTTP status codes are extensible, and it is not mandatory for HTTP applications to recognise the meaning of all registered status codes. A list of all of the status codes is given below.
1xx: Information
| Message | Description |
|---|---|
| 100 Continue | The server has only received a part of the request, but as long as it has not been rejected, the client can proceed with the request. |
| 101 Switching | The server switches protocol. |
2xx: Successful
| Message | Description |
|---|---|
| 200 OK | The request is OK. |
| 201 Created | The request is complete, generating a new resource. |
| 202 Accepted | For processing the request is approved but the processing is not complete. |
| 203 Non-authoritative Information | The entity header information is from a local or third party copy and not from the original server. |
| 204 No Content | In the response, a status code and a header are given but there is no entity-body in the response. |
| 205 Reset Content | For additional input, the browser should clear the form used for that transaction. |
| 206 Partial Content | The server returns partial data of the necessary size. Used in response to a request that specifies a header for the Set. The server must define the range the Content-Range header includes in the response. |
3xx: Redirection
| Message | Description |
|---|---|
| 300 Multiple Choices | A list of Links. The user can choose a connect and proceed to that location. Up to five addresses. |
| 301 Moved Permanently | The requested page has moved to a new url . |
| 302 Found | The requested page relocated to a new url temporarily. |
| 303 See Other | You will find the requested page under a different url. |
| 304 Not Modified | This is the response code to an If-Modified-Since or If-None-Match header, where the URL has not been updated since the date defined. |
| 305 Use Proxy | You must access the requested URL via the proxy specified in the Location header. |
| 306 Unused | In a previous version, the code was used. It won't be used anymore but the code is reserved. |
| 307 Temporary Redirect | The requested page has moved temporarily to a new url. |
4xx: Client Error
| Message | Description |
|---|---|
| 400 Bad Request | The server did not comprehend the request. |
| 401 Unauthorized | The page you are requesting requires a username and a password. |
| 402 Payment Required | You still can't use the code. |
| 403 Forbidden | Access to requested page is forbidden. |
| 404 Not Found | The server can not find the requested page. |
| 405 Method Not Allowed | The method established out in the request is not permitted. |
| 406 Not Acceptable | Only a response which the client does not accept can be generated by the server. |
| 407 Proxy Authentication Required | Before this request can be served you need to authenticate with a proxy server. |
| 408 Request Timeout | It took more time to request than the server was prepared to wait. |
| 409 Conflict | Due to a conflict the request could not be completed. |
| 410 Gone | The requested page is no longer available . |
| 411 Length Required | No specification is given for the "Content-Length." Without it, the server will not approve the request. |
| 412 Precondition Failed | The pre-condition given in the server 's request assessed to false. |
| 413 Request Entity Too Large | Since the request entity is too big the server would not accept the request. |
| 414 Request-url Too Long | Because the url is too long the server will not accept the request. It happens when you convert a "post" request with a long query information to a "get" request. |
| 415 Unsupported Media Type | The server will not approve the request as it does not support the mediatype. |
| 416 Requested Range Not Satisfiable | The requested byte range is not available and is out of bounds. |
| 417 Expectation Failed | This server could not meet the expectations provided in an Expect request-header field. |
5xx: Server Error
| Message | Description |
|---|---|
| 500 Internal Server Error | The request has not been completed. The server met a state of unexpectedness. |
| 501 Not Implemented | The request has not been finalised. The server didn't support the required functionality. |
| 502 Bad Gateway | The request has not been completed. The upstream server received an invalid response. |
| 503 Service Unavailable | The request has not been completed. Temporarily the server overloads or downs. |
| 504 Gateway Timeout | The gateway has timed out. |
| 505 HTTP Version Not Supported | The server does not support the "http protocol" version. |
No Sidebar ads