Server

http error

http error – http status

http error s are codes that help us understand whether a response has been successful or failed. Often, users do not see the codes returned in the browser, but these codes are returned to the client each time the browser interacts with the server.

http is a communication protocol used on the world wide web since 1990. http stands for “hyper text transfer protocol“. The HTTP protocol is the protocol that allows viewing web pages over the network. http protocol determines the exchange rules between client (PC) and server (server).

http status codes, on the other hand, are codes that help us understand whether a response was successful or unsuccessful. Often, users do not see the codes returned in the browser, but these codes are returned to the client each time the browser interacts with the server.

http status codes can help provide a better user experience for viewers using an application in terms of displaying the error message and the success message.

http status codes can be collected in 5 different groups. The total number of these codes can be up to 80. However, in this article, we will share the most popular and most used codes with you.

http status code
http status code

informative http error – http status codes (100-199)

 

http 100 ( continue )

It is an indication that everything went well so far and that the request has not yet been rejected by the server.

 

http 101 ( switching protocol )

At this stage, it indicates that the server has changed the protocol as requested by a client. The server then does a raise in the response header to indicate that the protocol has been changed.

 

http 102 processing ( webdav )

This HTTP status code indicates that the server has received and processed the request, but there is no response yet.

 

http 103 ( early hints )

This http 103 ( early hints ) is mainly used to return some response headers before the server sends an HTTP message.

  • Click for more detailed information about http 103 (Early Hints).

successful http status codes (200-299)

http 200 ( ok )

The HTTP 200 status code indicates that the response was successful. That is, the communication between client and server ran smoothly without any errors.

 

http 201 ( created )

This indicates that the request is not only successful, but a resource has also been created. This status code usually comes with a POST request as it identifies the resource sent to the server.

 

http 202 ( accepted )

This means that a client has requested to create something on the server, then the request has been accepted but is not yet complete as it still goes through some processing.

Requests may or may not be enforced as processing may not be permitted at the time of processing.

 

http 203 ( non-authoritative information )

This indicates a successful request, but the entity header has been changed from that of the originating server. Allows the agent to send an alert to residents when a change is applied.

 

http 204 ( no content )

This means that the sent request was received, but there is no additional data to send in the response payload. PUT method is mostly used for 204 response and can be cached by default.

 

http 205 ( reset content )

Here the request is processed successfully, but the response tells the user to reset the document view so the request returns to the original state it was received from the server.

 

redirect http status codes (300-399)

http 300 ( multiple choice )

This http code shows the multiple options or resources a user can choose from, and each option or resource can be uniquely identified.

This response code is rarely used, as there is no generally accepted way to select a particular response.

 

http 301 ( moved permanently )

Here, all future requests to the resource should be directed to a specific URL. It can be used to redirect from a page that no longer exists.

However, it is recommended to use this request only for GET or HEAD methods because it contains some bugs and not all user agents are compatible with it. This type of response can be cached by default.

 

http 302 ( found ) previously

This response is similar to the 301 HTTP status code. The difference here is that the requested resource has been temporarily moved to a specific thread.

But 302 has been replaced by 303 and 307. Just like with the 301 HTTP response code, it is recommended to use this request only for the GET or HEAD methods because not all user agents align with it.

 

http 303 ( see other )

This HTTP status code indicates that the response to this request was redirected to another URL. This status code is valid for any HTTP method.

 

http 304 ( not modified )

Here, there is no need to resubmit the requested resource as the user agent has a cached copy of the last resource. The goal is to minimize data transfer as the user agent already has a copy of the latest update.

 

http 307 (temporary redirect )

In this case, the response code indicates that the requested resource has been temporarily moved to another URL. The client is expected to continue using the original URL to make a request.

Here, unlike the 302 HTTP status code, the request method is guaranteed not to be changed during the redirect.

 

http 308 ( permanent redirect )

In this case, the requested resource is assigned a new permanent URL that allows requests to run smoothly. Unlike the 301 HTTP status code, which can be changed, the request method does not change during a redirect.

client error http status codes (400-499)

http 400 ( bad request )

This indicates that the received request could not be processed by the server due to an error that could be due to incorrect syntax. The server waits for some changes to be made when the next request is received, otherwise the same error will continue.

 

http 401 ( unauthorized )

In this case, authorization is required to access a received response. This http status code is similar to HTTP 403. Here, however, it is expected to have valid credentials for the request to be accepted.

 

http 403 ( forbidden )

This HTTP status code means that the user-client has valid data but access is denied by the server. Repeated attempts will not yield a successful response as a user, as the user is not allowed to have any rights over the resource in question.

http 404 ( not found )

This HTTP code means that the requested resource cannot be found by the server. This may be due to a temporary glitch and the resource may be available if another request is made in the future. For the most part, links that lead to a 404 are often referred to as broken links.

 

http 405 ( method not allowed )

This HTTP code means that a requested method is not supported for the requested resource even when recognized by the server. The resource may be expecting a GET or POST method, but if it receives a DELETE or PUT method, the request will be rejected as 405.

http 410 ( gone )

As the name suggests, this HTTP status code indicates that the requested resource is no longer available. Unlike the 404 status code, the results of this response are permanent. This response can be cached by default.

 

http 418  ( i’m a teapot )

This HTTP code is probably everyone’s favorite response code. It was defined in 1998 and is not expected to be defined by any HTTP server. It means that the server is permanently refusing to brew coffee because it is a teapot.

 

http 429 ( too many requests )

Here, the user-customer made too many requests in a given time frame. However, it is possible for the request header to indicate a response as to how long a client must wait before retrying the request. It is mainly used for rate limiting strategies for security purposes.

 

server error http status codes (500-599)

 

http error
http error

http 500 error ( internal server error )

Here it means that a particular request encountered an unexpected situation that caused it to be unable to complete the request. The user is not expected to see this HTTP status code on the web page.

 

http 501 error ( not implemented )

This HTTP status code indicates that the server does not support or have the requirements to complete a particular request. This means that the server the user-client is trying to access needs to be fixed.

 

http 502 error ( bad gateway )

This HTTP code indicates that the server received an invalid response from the server while making the request while acting as a proxy.

 

http 503 error ( service unavailable )

This HTTP status code indicates a temporary state. This means that the request to the server is currently unable to perform the action; this may be due to maintenance or the server is overloaded.

 

http 504 error ( gateway timeout )

This http status code indicates that the server is acting as a proxy, not sending the request within the expected timeframe. This fix is ​​expected to come from the server.

 

abandoned http status codes

http 305 ( use proxy )

This HTTP response code should no longer be used for security reasons, although it will still work.

 

http 306 ( unused )

This HTTP status is no longer used, it was used in the previous version of the HTTP / 1.1 specification.

You can find all http status codes in this RFC document.

You can access the list of all http status codes here.

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top button