Guide

Complete Guide to HTTP Status Codes

Share

Browsers show HTTP Status Codes when users view a particular online page. Moreover, it signifies the originating server has trouble processing our request.

These are signals from the server. Moreover, they inform us of the results of their response to our requests to access a particular site.

Several APIs use the most fundamental responses. Some wish to fully use HTTP’s library of codes to inform their customers of any issues. And develop their custom error signaling systems on top of those.

What are HTTP Status Codes?

Whenever a host serving a website answers an end user’s request, it generates an HTTP response. For example, end users could be browsers or crawlers.

Although each code has a unique meaning, most queries have the same results. For instance, different statuses that state a “redirect” share the same effect.

It contains codes from various standards, “RFCs (Request For Comments) from the IETF.” And a few extra codes are available in different widespread HTTP programs.

For example, an HTTP/1.1 specification includes the standard response message. Also, it’s related to RFC 7231.

A status code presents itself if the server cannot fulfil a query. And browsers cannot show the required information. Moreover, these errors would determine the response code.

What are the Categories of HTTP Status Codes?

Any number in an HTTP message more than 100 and below 600 is called the “status code.” There’re five groups or types used to categorize every HTTP status. For example, the code’s 1st number indicates either of five standard reply types.

  • 1xx

100 – 199 are “informative” statuses. These alert the user that the request’s header portion was already accepted. So servers would attempt to meet the client’s communication request.

There are two examples. The first is Applying an alternative protocol. The second is Informing browsers that their query would fail before delivering the content’s body.

  • 2xx

The “success” statuses are 200 – 299. They inform the consumer that their request has been granted. It means the query satisfies all validation criteria when a request is handled. It’s at the moment of submission.

  • 3xx

300 – 399 are statuses for “redirection.” They inform the user that the requested content is no longer accessible.

Thus, at the user’s anticipated location. Every browser must send a request to the newest address. Browsers should do this regardless of whether it is transitory or everlasting.

  • 4xx

The “client error” messages are 400 – 499. They all concern incorrect requests that clients made to servers. It could be provoked by several things, including timeouts or inaccurate URIs. Or a lack of authentication, etc.

A client supplying the wrong information should double-check that the inputs are accurate. It should be beforehand submitting the request.

  • 5xx

These “server error” messages are 500 – 599. They usually point to issues with overloaded servers or inaccessible hosts. But they might be directly connected to consumer requests that fail the host.

These failures could be transitory or prolonged. The browser should typically attempt the same request again.

HTTP Status Codes and Search Engine Optimization

Crawlers record every status they come across. They assess the domain’s healthiness and rank every page. Because of this, codes are essential for a portal’s search engine optimization (SEO).

  • The optimal code for a typical, regularly working website is HTTP 200. Users, bots, and hyperlinks all easily navigate across related pages.

Here we are not required to take any action and can comfortably continue to work. Understand that things are moving according to intent.

  • Regarding permanent URL redirection, 301 code is still the technique of preference. Whenever we need to transfer an address to the other, 301 redirects could be used.

We could send Users and bots on such a page to the newest link.Using 302 redirections for long-term modifications is not something we tell.

Using a 302 would make web crawlers see a redirect as transitory. It might prevent them from passing along the SEO’s beneficial “link juice” that perhaps a 301 does. Remember, “link juice” sees if a web page is worthwhile to promote.

  • HTTP 404 indicates that the host could not find the requested content or page. Moreover, one frequent misunderstanding seems to be an excellent SEO practice. That is 301 redirecting links that produce a 404 response to a specific site’s main page.

    It could frustrate people. It’s because people are unaware that the place they are attempting to reach doesn’t exist.

    Unless the sites generating 404 are top-authority ones because of enormous traffic. Or contain the exact URL people have been looking for. Then only should use 301 redirects to the best relevant internal web page available.

    Despite these cases, it could be necessary for a Domain to produce the 404 intentionally. It’s to avoid being crawled and frequently indexed by search results.

    Ecommerce businesses, for instance, might generate 404 results whenever things disappear from stock. Thus these web pages become ideal for developing customized creative 404 pages.

  • HTTP 410 indicates that the content is no longer accessible from the host. And that no link forwards has been configured. We are redirecting bots and users to a discontinued page. So delete all references or linkages within your website if you spot these.
  • HTTP 500 is a standard server blunder that will prevent visitors from accessing our website. Users would lose, but our “link juice” would vanish quickly. Because search engines desire well-maintained domains, we should analyze these statuses. And settle troubles as soon as possible.
  • HTTP 503 error indicates that some service is not available. It informs search results that the content will be unavailable for a brief period. But it ensures that they should return soon.
  • There are unofficial statuses that are not defined by any standards. For example, Nginx and IIS (Internet Information Services) host extends 4xx’s error category. These two state faults with the browser’s request.

           Cloudflare’s reverse proxy feature extends the 5xx error category. It indicates problems with the originating host. Moreover, AWS’s Elastic Load Balancer now has a few more configurable response codes.

Complete Guide and HTTP Status Codes

We have addressed the most frequent ones here and some of the unrecognized states we could still see.

100s: Informational

The 100s are just informative. It shows that the browsers have sent a query to the host and are awaiting a reply.

  • Status 100 for “Continue”The host has accepted the query header from browsers and is waiting for the request’s body.
  • Status 101 for “Switching Protocol”Browsers requested a protocol adjustment, which was granted by the server.
  • Status 102 for “Processing”The host is processing the browser’s query, yet no reply from the host is still accessible.
  • Status 103 is the “Early Hints”Here the server sends specific early indications to browsers to preload necessary materials. It is beforehand providing a final answer.

200s: Successful

These statuses notify the browsers that things are working correctly.

    • Status 200 is the “OK”The request was granted, and the necessary reply was delivered. The reaction would vary based on the protocol function. Like GET, POST, HEAD, TRACE, or PUT.
    • Status 201 is the “Created”The browser’s query was successful, and new content was produced. It’s the standard answer to PUT/POST queries.
    • Status 202 is the “Accepted”The host welcomed the browser’s query but is yet to respond.
    • Status 203 is the “Non-Authoritative Information”The meta-data presently accessible may vary. Due to this, the host delivers meta-data that isn’t from the originating server. Thus, it is utilized whenever the data is obtained from a 3rd party or a regional version.
    • Status 204 is the “No Content”

The host has no material to send after a successful query. But, it could send prevailing header data, causing a refresh of the user agent’s cache headers.

  • Status 205 is the “Reset Content”The host has responded to our browser’s request to alter the content viewing.
  • Status 206 is the “Partial Content”The host delivered some of the material. It is due to our browsers querying it using the Ranging header.
  • Status 207 is the “Multi-Status”Here multiple codes are needed in a single occurrence. So the host responds to data from various sources.
  • Status 208 is the “Already Reported”The host gives data that the inner parts of a WebDAV component have previously been reported. It is to prevent needless evaluation. This reply is usually sent after a 207 message.
  • Status 226 is the “IM Used”Our browsers successfully used the GET technique. It is to obtain an upgraded version of previous cache content from the host. The answer is provided whenever one or more minor changes are made to the requested data.

300s: Redirection

These state that the intended material has been relocated. And informs the browsers how it could be accessed.

  • Status 300 is the “Multiple Choices”There are many answers to the request sent by the browsers.
  • Status 301 is the “Moved Permanently”The intended content has been permanently relocated to a new place. Due to this, the host directs the browsers to a different link.
  • Status 302 is the “Found”Our browsers have notified us that the requested content has been temporarily relocated. But all future queries should use the same address.
  • Status 303 is the “See Other”The host notifies the browsers that the requested information is in a new domain. But, it needs to be accessed using the GET function.
  • Status 304 is the “Not Modified”The delivered answer informs browsers that the requested item has not been updated. It has been since its last access. As a consequence, the cached variant in browsers must be used.
  • Status 305 is the “Use Proxy”To supply the requested data, the host requires a proxy. Unfortunately, the said code is no longer used. Most modern browsers wouldn’t recognize it due to safety concerns.
  • Status 306 is the “Switch Proxy”To fulfill future requests, the host needs the usage of specific proxies. Moreover, due to safety considerations, this reply format is not accepted.
  • Status 307 is the “Temporary Redirect”The host notifies browsers that the intended item is temporarily housed elsewhere. It is a substitute for the 302 code. Still, an identical HTTP function should be used when requesting a service.
  • Status 308 is the “Permanent Redirect”Browsers are attempting to retrieve content that has been permanently relocated. It is in a different location. Moreover, it is a counterpart to the 301 response. An HTTP request function cannot be changed with this sort of redirection.

400s: Client Error

These reveal the existence of client-caused errors.

    • Status 400 is the “Bad Request”There is a problem on the consumers’ end, so the host cannot respond.
    • Status 401 is the “Unauthorized”The host needs authorization before allowing the browsers to access the requested information.
    • Status 402 is the “Payment Required”It is designated for online payments, as the name implies. Moreover, it is not commonly utilized.
    • Status 403 is the “Forbidden”The browser is refused access to the desired resource. It is because the client lacks appropriate permissions.
    • Status 404 is the “Not Found”The targeted material is not currently accessible. But in the future, it could become attainable.
    • Status 405 represents “Method Not Allowed.”The host understands the request protocol chosen by the browsers. Yet it needs to be replaced to offer the requested material.
    • Status 406 is the “Not Acceptable”The host notifies the consumer that no resources match the parameters. It is from parameters specified by browsers.
    • Status 407 is the “Proxy Authentication Required”Identical to the 401 response, but the host needs proxy authorization.
    • Status 408 is the “Request Timeout”The host ran out of time while awaiting the user to deliver a request within the deadline.
    • Status 409 is the “Conflict”As a consequence of a mismatch with the current status of the sought item, the host cannot respond.
    • Status 410 is the “Gone”It is similar to the 404 response. It signifies that the requested content will no longer be accessible in the future.
    • Status 411 is the “Length Required”The host alerts browsers. For providing requested content, the query must have a specific information length.
    • Status 412 is the “Preconditioned Failed”Browsers sent a request containing prerequisites that the host could not meet.
    • Status 413 represents “Payload Too Large.”Since the query is too massive, the host refuses to handle it.
    • Status 414 is the “URL Too Long”The host can’t handle the request submitted by the browsers. It is because the consumer encoded excessive information as a user query. Subsequently, it is transmitted like a GET function.
    • Status 415 is the “Unsupported Media Type”The host has rejected the request since it doesn’t accept the requested file format.
    • Status 416 is the “Range Not Satisfiable”The host is unable to supply the consumer with the requested part.
    • Status 417 is the “Expectation Failed”The browsers issued an Expect header query to the host, yet this host could not meet the criteria.
    • Status 418 is the “I’m a Teapot”It’s the Easter Egg protocol from an April Fools’ Day prank. Hosts are not supposed to support this method, yet if you’re wondering how it works, see the Teapot site of Google.
    • Status 421 is the “Misdirected Request”The application’s request was routed to a different host that could not respond.
    • Status 422 is the “Unprocessable Entity”The browser’s query had syntactic flaws, so it could not process.
    • Status 423 is the “Locked”Since the required asset is locked, entry to it has been prohibited.
    • Status 424 is the “Failed Dependency”The browser’s query terminated since it depended on another request that also dropped.
    • Status 425 is the “Too Early”Since the query could be repeated, the host declines to handle it.
    • Status 426 represents “An upgrade is required”The host does not support the present protocol, so it delivers the Upgrade header to the consumer. And including a request for such a protocol update.
    • Status 428 is the “Precondition Required”

As for the host to execute the browser’s query, criteria must be specified.

  • Status 429 for “Too Many Requests”Browsers sent too many queries to the host in the given waiting period.
  • Status 431 is the “Request Header Fields Too Large”The host is not processing the consumer’s request. It is because the request headers given are much bigger. Only after parameters are resized is the host ready to perform the query.
  • Status 451 represents “Unavailable For Legal Reasons.”Because of legal considerations, the host cannot provide the requested content.

500s: Server Error

It signifies that the host did not process a query.

  • Status 500 for “Internal Server Error” The host sends a generalized message when an undesirable circumstance occurs.
  • Status 501 is the “Not Implemented” The host states that it cannot complete the query or that the protocol is not recognized.
  • Status 502 is the “Bad Gateway” The host responds that it served as an entry point. Or as proxies for an underlying host that returned an erroneous result.
  • Status 503 is the “Service Unavailable” The host cannot handle the request since it is perhaps overburdened or under upkeep.
  • Status 504 is the “Gateway Timeout” The originating host has not responded to a secondary host, which now acts as proxies or gateway. As a consequence, it is unable to respond to the user.
  • Status 505 is the “HTTP Version Not Supported” The host does not support the protocol used in the query.
  • Status 506 is the “Variant Also Negotiates” The host cannot choose whichever (better) variant to offer as a reply. HTTP permits many versions of the service to live under an exact address. As a result, a server setup issue frequently causes it.
  • Status 507 is the “Insufficient Storage” The host cannot keep the representations of the requested data. It is for that which is required to complete the query correctly.
  • Status 508 is the “Loop Detected” The host has discovered an endless loop and cannot handle the request.
  • Status 510 is the “Not Extended” The host implements extra extensions. For example, it must be indicated in the query header to enable the host to satisfy it.
  • Status 511 is the “Network Authentication Required” The browser must offer authorization for the host to provide network access.

FAQ

How can you Avoid Website Errors?

Evaluating user activities is the most effective technique to avoid web page faults. One could do it using data analysis and predict every potential issue. Restricting input data may also assist in decreasing risks.

How to Avoid 404 Errors?

Inform users that the content they are seeking cannot be accessible. Adopt pleasant and welcoming phrases. Ensure the 404 pages have the same style and appearance as most of your website.

Try to include linkage to the most critical blogs or pages, along with a link to the main page of your website. Moreover, think about making it possible for individuals to report broken links.

How to Avoid Network Errors?

Examine the logs and firewall configuration. There might be an extensive set of limiting rules. For example, check that no security mechanisms block search engine bot IPs.

What to do if you cannot discover a Fix?

If you cannot find a fix to an error, you could contact your hosting provider. You also could contact a Server Administrator to find out what is causing the issue.

Conclusion

HTTP Status Codes contribute to their use as a troubleshooting tool. Understanding what these statuses imply will ensure the upkeep of the platform’s productivity.

You can quickly solve issues on your page if you understand some of the most prevalent ones.

If you operate your DNS host, check to be sure it’s in good shape and not overcrowded. Also, use a URL Inspection program to ensure that your address gives the correct code.

Chris Wagner

I am Chris Wagner, Having 12+ years of experience in the Hosting industry.

Published by
Chris Wagner

Recent Posts

9 Best Student Hosting for 2025

Hello, Gen Z! Ready to fly high with your dreams? Let no one stop you…

6 months ago

5 Best HideMyAss Alternatives (#3 is Just Awesome)

Let's talk about HideMyAss Alternatives! But first, let us talk about HideMyAss. If you’re interested…

6 months ago

Kadence WP Review (2025)

These days the theme market is flooded and users are spoiled by choices. But if…

6 months ago

10 Best Tested Video Hosting Sites

Thinking of starting a video log or want to host your video on a video…

6 months ago

9 Best Ecommerce Hosting Providers in 2025

So, you‘re looking for the best ecommerce hosting company for your needs? No matter whether…

6 months ago

Turnkey Internet Review: My Honest Opinion + Pros & Cons

Why Trust Us "We have been a paying customer for Turnkey Internet since March 2019.…

6 months ago