Netscape ENTERPRISE SERVER 6.0 - NSAPI PROGRAMMER GUIDE Manual page 320

Responses
Some common status codes are shown in Table E-2.
Table E-2
Status code
200
201
206
302
304
400
401
403
404
408
411
413
414
416
320 Netscape Enterprise Server NSAPI Programmer's Guide • November 2001
Common HTTP status codes
Meaning
OK; request has succeeded for the method used (GET, POST, HEAD).
The request has resulted in the creation of a new resource reference by the
returned URI.
The server has sent a response to byte range requests.
Found. Redirection to a new URL. The original URL has moved. This is
not an error; most browsers will get the new page.
Use a local copy. If a browser already has a page in its cache, and the page
is requested again, some browsers (such as Netscape Navigator) relay to
the web server the "last-modified" timestamp on the browser's cached
copy. If the copy on the server is not newer than the browser's copy, the
server returns a 304 code instead of returning the page, reducing
unnecessary network traffic. This is not an error.
Sent if the request is not a valid HTTP/1.0 or HTTP/1.1 request. For
example HTTP/1.1 requires a host to be specified either in the Host
header or as part of the URI on the request line.
Unauthorized. The user requested a document but didn't provide a valid
username or password.
Forbidden. Access to this URL is forbidden.
Not found. The document requested isn't on the server. This code can also
be sent if the server has been told to protect the document by telling
unauthorized people that it doesn't exist.
If the client starts a request but does not complete it within the keep-alive
timeout configured in the server, then this reponse will be sent and the
connection closed. The request can be repeated with another open
connection.
The client submitted a POST request with chunked-encoding, which is of
variable length. However, the resource or application on the server
requires a fixed length - a "content-length" header to be present. This code
tells the client to resubmit its request with content-length.
Some applications (eg. certain NSAPI plug-ins) cannot handle very large
amounts of data, so they will return this code.
The URI is longer than the maximum the web server is willing to serve.
Data was requested outside the range of a file.