ErrorTech News

List Of HTTP Error Codes (Explained)

By June 13, 2018 No Comments
HTTP Error Codes

Sharing is caring!

Internet Is Vast thing it plays a major impact on our in life. It’s  one of most complex network  and it is piece of engineering marvel.

But Some time it show some HTTP error codes and for most us this is unknown as result most of get panicked easily in the open world there are some people and organisation are there who take advantage this and make money out of it  they make you believe that its your device major error  and they use void to penetrate your pocket easily  and lack of knowledge makes you believe them and throwing tons money.

So in this blog we are going en light with you this error code so next you neither get panicked and lose money .

2xx Series HTTP Error Codes

200 OK

Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request, the response will contain an entity describing or containing the result of the action

201 Created

The request has been fulfilled, resulting in the creation of a new resource.

202 Accepted

The request has been accepted for processing, but the processing has not been completed. The request might or might not be eventually acted upon, and may be disallowed when processing occurs.

203 Non-Authoritative Information (since HTTP/1.1)

The server is a transforming proxy  that received a 200 OK from its origin, but is returning a modified version of the origin’s response.

204 No Content

The server successfully processed the request and is not returning any content.

205 Reset Content

The server successfully processed the request, but is not returning any content. Unlike a 204 response, this response requires that the requester reset the document view.

206 Partial Content 

The server is delivering only part of the resource  due to a range header sent by the client. The range header is used by HTTP clients to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.

207 Multi-Status (WebDAV)

The message body that follows is by default an XML message and can contain a number of separate response codes, depending on how many sub-requests were made.

208 Already Reported 

The members of a DAV binding have already been enumerated in a preceding part of the (multistatus) response, and are not being included again.

226 IM Used 

The server has fulfilled a request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.

3xx Series HTTP Error Codes

300 Multiple Choices

Indicates multiple options for the resource from which the client may choose (via agent-driven content negotiation). For example, this code could be used to present multiple video format options, to list files with different filename extensions, or to suggest word-sense disambiguation.[20]

301 Moved Permanently

This and all future requests should be directed to the given

302 Found

Tells the client to look at (browse to) another url. 302 has been superseded by 303 and 307. This is an example of industry practice contradicting the standard. The HTTP/1.0 specification (RFC 1945) required the client to perform a temporary redirect (the original describing phrase was “Moved Temporarily”),but popular browsers implemented 302 with the functionality of a 303 See Other. Therefore, HTTP/1.1 added status codes 303 and 307 to distinguish between the two behaviors. However, some Web applications and frameworks use the 302 status code as if it were the 303.

303 See Other (since HTTP/1.1)

The response to the request can be found under another URI using the GET method. When received in response to a POST (or PUT/DELETE), the client should presume that the server has received the data and should issue a new GET request to the given URI.

304 Not Modified 

Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-None-Match. In such case, there is no need to retransmit the resource since the client still has a previously-downloaded copy.

305 Use Proxy (since HTTP/1.1)

The requested resource is available only through a proxy, the address for which is provided in the response. Many HTTP clients such as Mozilla and Internet Explorer) do not correctly handle responses with this status code, primarily for security reasons.

306 Switch Proxy

No longer used. Originally meant “Subsequent requests should use the specified proxy.

307 Temporary Redirect (since HTTP/1.1)

In this case, the request should be repeated with another URI; however, future requests should still use the original URI. In contrast to how 302 was historically implemented, the request method is not allowed to be changed when reissuing the original request. For example, a POST request should be repeated using another POST request.

308 Permanent Redirect 

The request and all future requests should be repeated using another URI. 307 and 308 parallel the behaviors of 302 and 301, but do not allow the HTTP method to change. So, for example, submitting a form to a permanently redirected resource may continue smoothly.

This class of status codes indicates the action requested by the client was received, understood and accepted.

4xx Series HTTP Error Codes

444 No Response

Used internally to instruct the server to return no information to the client and close the connection immediately.

494 Request header too large

Client sent too large request or too long header line.

495 SSL Certificate Error

An expansion of the 400 Bad Request response code, used when the client has provided an invalid client certificate.

496 SSL Certificate Required

An expansion of the 400 Bad Request response code, used when a client certificate is required but not provided.

497 HTTP Request Sent to HTTPS Port

An expansion of the 400 Bad Request response code, used when the client has made a HTTP request to a port listening for HTTPS requests.

499 Client Closed Request

Used when the client has closed the request before the server could send a response.

440 Login Time-out

The client’s session has expired and must log in again.

449 Retry With

The server cannot honour the request because the user has not provided the required information.

451 Redirect

Used in Exchange ActiveSync when either a more efficient server is available or the server cannot access the users’ mailbox. The client is expected to re-run the HTTP AutoDiscover operation to find a more appropriate server.

5xx Series HTTP Error Codes

500 Internal Server Error

A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.

501 Not Implemented

The server either does not recognize the request method, or it lacks the ability to fulfil the request. Usually this implies future availability (e.g., a new feature of a web-service API).

502 Bad Gateway

The server was acting as a gateway or proxy and received an invalid response from the upstream server.

503 Service Unavailable

The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state.

504 Gateway Timeout

The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.

505 HTTP Version Not Supported

The server does not support the HTTP protocol version used in the request.

506 Variant Also Negotiates 

Transparent content negotiation for the request results in a circular reference.

507 Insufficient Storage (WebDAV;)

The server is unable to store the representation needed to complete the request.

508 Loop Detected (WebDAV;)

The server detected an infinite loop while processing the request (sent in lieu of 208 Already Reported).

510 Not Extended 

Further extensions to the request are required for the server to fulfill it.

511 Network Authentication Required 

The client needs to authenticate to gain network access. Intended for use by intercepting proxies used to control access to the network used to require agreement to Terms of Service before granting full Internet access via a Wi-Fi hotspot).

Hope You like this blog. In case you face any issue with your internet and do not find a way to resolve it, know that we are here to help you. You can live chat with our technical experts and get help instantly or  you can book a repair job with techyuga.

Book A Repair Job

Sharing is caring!

AK Azad

Author AK Azad

Technology has always been astounding for him. A Biker by Heart ,Loves to travel, always has an eye out for new technology. Loves to share info on new tech with everyone. An Operation Manager turned Digital Marketer Also A Computer Science Engineer.

More posts by AK Azad

Leave a Reply