Server Header Responses Explained
Whenever we visit a web page, our computer will request data from a server using the HTTP protocol. Right before the requested page is received and rendered in our browser, the web server that hosts the web page will return the HTTP header that has the status code. The status code provides information about the condition of the requested resource. If everything’s OK, a normal web page gets the status code as 200. Of course, we don’t tend to see 200 responses – it’s only when there’s a problem that we see some of the other server header responses, like a 404 Not Found.
Origin of HTTP Status Code
As a part of the HTTP 0.9 specification, the World Wide Web Consortium (W3C) established HTTP status codes in 1992. Tim Berners-Lee, who invented the web and the first web browser in 1990, defined the status codes.
Server Headers Responses Explained
- 200:OK – Standard response for successful requests
- 301:Moved Permanently – Resource permanently moved to a different URL
- 302:Found – Requested resource was found under a different URL but the client should continue to use the original URL
- 304:Not Modified – Resource not modified since the last request
- 404:Bad Request – Syntax of the request not understood by the server (server itself was found, but that the server was not able to retrieve the request page)
- 500:Internal Server Error – Request unsuccessful because of an unexpected condition encountered by the server
- 503:Service Unavailable – Request unsuccessful to the server being down or overloaded
For Infographic on the same, click here.
