This tool will check the header code and information contained within. The following is a list of server response codes and the applicable description. Most of us know what a 404 response and a 200 response is, but what about 500 or 304, the difference between a 307 and 302. This is a great resource to reference for those of us, like me, who don’t have it all in my head. The actual tool is on the next page, click through for the list and the tool to check your response headers are returning the correct status.
Server Status Code Descriptions
- 200 OK The request has succeeded. The information returned with the response is dependent on the method used in the request.
- 301 Moved Permanently The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs.
- 302 Found The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests.
- 304 Not Modified If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server SHOULD respond with this status code. The 304 response MUST NOT contain a message-body, and thus is always terminated by the first empty line after the header fields.
- 307 Temporary Redirect The requested resource resides temporarily under a different URI. Since the redirection MAY be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.
- 404 Not Found The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
- 410 Gone The requested resource is no longer available at the server and no forwarding address is known. This condition is expected to be considered permanent.