HTTP status codes are an essential part of the Internet and are used to describe the results of requests to web servers. There are a total of five different categories of status codes, each of which has a specific meaning. On our website you will find a comprehensive list of all HTTP status codes as well as detailed explanations of each category.
Our HTTP Status Codes Blog
Our blog on HTTP status codes provides an in-depth look at the meaning and use of various codes in web traffic. From common 404 errors to redirects and server errors, learn how they work and how to deal with them to improve your website's performance and optimize user experience. Discover best practices, case studies, and useful tips to avoid potential problems and realize the full potential of your website.
Section 1: What is the xmlrpc.php file and where is it foundThe xmlrpc.php file is an important component in WordPress, one of the world's leading content management systems (CMS) for creating and ...
Web performance and the resulting user experience are central aspects for the success of any website. One significant factor that affects this performance is HTTP status codes, especially in the co...
HTTP, or the Hypertext Transfer Protocol, is the backbone of the internet. It's the standard mechanism through which web browsers request data from web servers and receive this data. But what exact...
In a digitally dominated world, where websites increasingly serve as the primary face of brands, companies, and individuals, small mishaps can have severe implications. A wrong click, a misguided p...
For more blog articles click here
All status codes at a glance
The HTTP status codes in the range 100 to 199 are informational codes. They are used by the server to tell the client that the request has been received and that more information will follow.
The transmission protocol is changed at the request of the client
the cache was not able to validate the response because the origin server could not be reached
the cache is intentionally disconnected from the rest of the network
the cache has heuristically chosen a freshness time greater than 24 hours and the age of the answer is greater than 24 hours
The HTTP status codes in the range from 200 to 299 are success codes. They are used by the server to tell the client that the request was successful and that the requested information is included in the response.
A cached copy was used to provide the meta information. Data may not be up to date.
the client should reset the document to its original state. The request was successful
the requested part of the resource was submitted. The request was successful.
Using an XML document, several status codes are transmitted regardless of the operation performed
Members of the WebDAV session have already been nominated, and therefore will not be nominated again
a change in content encoding, media type or similar
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
The HTTP status codes in the range 300 to 399 are redirect codes. They are used by the server to tell the client that the requested resource is available at a different URL and that the client should redirect to that URL.
the redirects do not point to the requested resource itself, but to another page
The resource does not need to be retransmitted because no change has taken place
The ressouce is temporarily available under a new URL. The new call must be based on the same method
The HTTP status codes in the range 400 to 499 are client error codes. They are used by the server to tell the client that the request failed due to an error by the client.
Pre-conditions were not satisfactory, the request was not successful
The HTTP status codes in the range from 500 to 599 are server error codes. They are used by the server to tell the client that an error has occurred that prevented the request from being processed.