Home
 Products
 Download
 Buy
 Support
- F.A.Q.
- Error Codes
-- Winsock Errors
-- HTTP 1.0 Errors
-- HTTP 1.1 Errors

- Configuration
- Release Notes
- Year 2000

 Beta Area
 Contacts
 About Us




Server Status Code Definitions

From HTTP/1.0 - RFC1945
When you follow a link, or type in a web address, your local ISP sends that request to the appropriate server - usually the "www.company.com" part of the original address.

That server then tries to deliver the requested page to you.

The server also registers whether or not it has been able to deliver that request successfully, and generates a "Status Code".

Mostly, these messages are unseen by the user - especially when the request is successful. On other occasions, they may point to the reasons for any problem in displaying the requested page. These are the 400 and 500 series codes.

2xx
Successful Access
This range of codes indicates that the client's request was successfully received, understood, and accepted.
200
OK
The request has succeeded.
The server also sends extra information to your browser dependent on the method used in the request, as follows:
  • GET - an entity (a "page") corresponding to the requested resource is sent
  • HEAD - the server sends the page header, and nothing else (your browser uses this to decide whether the copy in your cache needs updating
  • POST - an entity (a "page") describing or containing the result of the action.
201
Created
A new resource (a "page") has been created, and your browser should display the address of this page.
202
Accepted
This tells your browser that your request has been accepted, but not yet completed (this is usually some background process).
204
No Content
The server has fulfilled the request but there is no new information to send back.

You will see no change in your browser.
3xx
Redirection
This class of status code indicates that further action needs to be taken by the user agent (your browser) in order to fulfill the request.
300
Multiple Choices
This response code is not directly used by HTTP/1.0 applications, but serves as the default for interpreting the 3xx class of responses.

It means that the requested resource is available at one or more locations. If the server has a preferred choice, it should include the URL in a Location field; user agents (browsers) may use this field value for automatic redirection.
301
Moved Permanently
The requested resource has been assigned a new permanent URL and any future references to this resource should be done using that URL. Clients with link editing capabilities should automatically relink references to the Request-URI to the new reference returned by the server, where possible.

The new URL must be given by the Location field in the response. Unless it was a HEAD request, the Entity-Body of the response should contain a short note with a hyperlink to the new URL.

If the 301 status code is received in response to a request using the POST method, the user agent must not automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.

Note: When automatically redirecting a POST request after receiving a 301 status code, some existing user agents will erroneously change it into a GET request.
302
Moved Temporarily
The requested resource resides temporarily under a different URL. Since the redirection may be altered on occasion, the client should continue to use the Request-URI for future requests.

The URL must be given by the Location field in the response. Unless it was a HEAD request, the Entity-Body of the response should contain a short note with a hyperlink to the new URI(s).

If the 302 status code is received in response to a request using the POST method, the user agent must not automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.

Note: When automatically redirecting a POST request after receiving a 302 status code, some existing user agents will erroneously change it into a GET request.
304
Not Modified
If the client has performed a conditional GET request and access is allowed, but the document has not been modified since the date and time specified in the If-Modified-Since field, the server must respond with this status code and not send an Entity-Body (the full page) to the client. Header fields contained in the response should only include information which is relevant to cache managers or which may have changed independently of the entity's Last-Modified date. Examples of relevant header fields include: Date, Server, and Expires. A cache should update its cached entity to reflect any new field values given in the 304 response.
4xx
Client Error
The 4xx class of status code is intended for cases in which the client seems to have erred. More simply, it means that the server can't find the address you've given it.

Servers will send your browser a page with the status code number on it (but little more explanation).
400
Bad Request
The request could not be understood by the server due to malformed syntax - perhaps because you've typed an illegal character, or put in too many slashes (///).
401
Unauthorized
The request requires user authentication (which hasn't been supplied, or which is incorrect).
403
Forbidden
The server understood the request, but is refusing to fulfill it.

This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
404
Not Found
The server has not found anything matching the Request-URI (the "address"). This may mean that you have typed a wrong address, or the page which once was there has now been removed.
5xx
Server Error
Response status codes beginning with the digit "5" indicate cases in which the server is aware that it has erred or is incapable of performing the request.

If you see one of these, there is nothing you can do about it, but try again later (or contact the webmaster).
500
Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.
501
Not Implemented
The server does not support the functionality required to fulfill the request. This is the appropriate response when the server does not recognize the request method and is not capable of supporting it.
502
Bad Gateway
The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill your request.
503
Service Unavailable
The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition.

Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.