Site Monitoring

HTTP Status codes

General - Status codes

Of all these possible errors you are only ever likely to see a handful when using Site Vigil.

The error codes are encoded into decimal ranges. For the full set of error codes please refer to

Site Vigil web site or RFC2616 for the authoritative explanation. Basically any code less than 400 is a warning or success code, anything above 400 represents an error.

200The request was successful. Hopefully the most frequent status code.
404The resource request was not found. This is the code returned for missing pages or graphics. Viruses will often attempt to access resources that do not exist, so the error does not necessarily represent a real problem.
403Access to a resource is not allowed. The most frequent case of this occurring is when directory listing access is not allowed.
304The resource has not been modified. The request is successful but the data does not need refreshing, the requesting agent can use a previously cached copy.
302The resource has moved elsewhere. The response gives details of the new location of the resource.
206The request was canceled before it could be fulfilled. Typically the user gave up waiting for data and went to another page. Some download accelerator programs produce this error as they submit multiple requests to download a file at the same time.
500The server had some sort of internal error trying to fulfil the request. The client may see a partial page or error message. It's a fault in the server and happens all too frequently.

© Copyright Silurian Software 2001 thru 2013