Web Codes
Informational |
||
100 |
Continue |
|
101 |
Switching Protocols |
|
Successful Transactions |
||
200 |
OK - The request was fulfilled. |
|
201 |
Created - The POST request was completed successfully. |
|
202 |
Accepted - Request accepted for processing of unknown
type. Rare. |
|
203 |
Non-Authoritative
Information - Request partially fulfilled. |
|
204 |
No Content |
|
205 |
Reset Content |
|
206 |
Partial Content |
|
Redirection Transactions |
||
300 |
Permanent
Relocation - The requested resource has been permanently moved to a
new URL. Usually accompanied by Location: newURL which
automatically connects to the new URL. |
|
301 |
Moved Target - The page you were attempting to reach has been moved. This move is Most likely to be permanent, but it is possible that this is only a temporary move. |
|
302 |
Moved temporarily/Redirect
- You will get this error if someone has moved the target page for only a
short amount of time. You will be forwarded to the correct URL as this
relocation is only temporary. Requested resource found, but at a
different URL. You’ll get a 302 Redirection if you omit the trailing slash
when pointing at a directory (sometimes called a malformed request). |
|
303 |
Another temporary
relocation - This error code is much the same as error code 302, but the web
page was requested slightly differently. As with error code 302, you will
probably be forwarded to the correct URL. |
|
304 |
Not Modified - Unmodified
data not returned in response to a GET request with the If-Modified-Since
field. Occurs when a browser requests data found in cache. |
|
305 |
Use Proxy |
|
306 |
(Unused) |
|
307 |
Temporary Redirect |
|
Client Error Messages |
||
400 |
Bad Request - The
request could not be understood by the server due to bad syntax. You should
not repeat the request without modifications. Error in request syntax. |
|
401 |
Access
denied/Unauthorized - This usually shows up when you have tried to access a
file or page that requires a login and password and you typed it incorrectly.
Alternatively, you may simply not have permissions for that page or file. You
should only retry the request if you know you authorization Request requires an Authorization: field, and
the client did not provide one. This response is accompanied by a list of
acceptable authorization schemes use WWW-Authenticate response
headers. Error 401 can be part of a client/server dialogue to negotiate
encryption and user authentication schemes. |
|
402 |
Payment Required - The
requested operation costs money, and the client did not specify a valid Chargeto
field. Payment was required in order
to access the requested web page. The message should give a specification of
charging schemes which are acceptable. |
|
403 |
Forbidden - Request
for forbidden resource denied. Sometimes
you will get these by accident if the webmaster has incorrectly set the
permission levels for a file or page. Even if you have a valid login and
password for this file/URL, you will still be denied access. |
|
404 |
Requested URL not
found Page not found - Requested resource not found. This
is the most common one you will see. There are generally two causes. One is
that you typed the URL incorrectly (or the link you clicked on was typed
incorrectly), and the other is that the HTML page you are trying to view does
not exist anymore. Make sure that the Web address (URL) that you typed in
exactly matches the address you were given. Check that the capitalization
matches, spelling, and punctuation, like dots (.) and slashes (/), are
correctly placed. Be sure you are using the forward slash (/) and not the
backward slash (\). |
|
405 |
Method Not Allowed - A 405 error means that the folder where
dtSearch Web is installed does not have "Execute" permission
enabled. |
|
406 |
None Acceptable - The server has found a resource matching the request URL, but not one that satisfies the conditions identified by the Accept and Accept-Encoding request headers. |
|
407 |
Proxy Authentication Required - This code is reserved for future use. It is similar to 401 (Unauthorized) but indicates that the client must first authenticate itself with a proxy. HTTP/1.0 does not provide a means for proxy authentication |
|
408 |
Request Time-Out -
The client did not produce a request within the time the server was prepared
to wait. |
|
409 |
Conflict -
The request could not be completed due to a conflict with the current state
of the resource. |
|
410 |
Gone - The
requested resource is no longer available at the server and no forwarding
address is known. |
|
411 |
Length Required - Authorization Refused - The request credentials provided by the client were rejected by the server or insufficient to grant authorization to access the resource |
|
412 |
Precondition Failed |
|
413 |
Request Entity Too Large |
|
414 |
Request-URL Too Large |
|
415 |
Unsupported Media Type |
|
416 |
Requested Range Not Satisfiable - When a client sends
acceptable file size parameters to the server and the user requests a file
that does not meet these parameters. |
|
417 |
Expectation Failed |
|
Server Error Messages |
||
500 |
Internal server
error – Page not available - The server has encountered an internal
error and cannot continue processing your request. This message is generated when an unexpected (read undefined) error
occurs. |
|
501 |
Not Implemented - Request
okay but denied because server doesn't support transaction method. Whatever you tried to do, the server
software is not designed to do it, or is not configured to do it. The server
simply does not support the functionality required to fulfill the request.
Usually you will see this because of the way you tried to authorize with a
login and password. |
|
502 |
Bad Gateway - The
server received an invalid responses from the upstream server it accessed in
attempting to fulfill the request. |
|
503 |
Service Temporarily
Unavailable Out of Resources - There is too much going on with the server. It
could be too many processes running or too many users. It's temporary, so
check it later. |
|
504 |
Gateway Timed Out -
The server is currently unable to handle the request due to a temporary
overload or maintenance of the server. It couldn't complete your request in
the allotted amount of time. You can also get this message if your connection
is extremely slow. The situation is almost always temporary and you should
try again after waiting for a bit. |
|
505 |
HTTP Version not
Supported - Server does not or refuses to support the HTTP version
that was used by the client to request information. |
|
8181 |
Certificate has expired (secure server only). |
|
12045 |
Invalid Certificate |
|
Failed
DNS Lookup |
The IP address of
the Web site could not be located by the ISP's domain name server or the
server is too burdened to process the request |
|