The client program is unable to locate or connect to the server. This
is frequently caused by a bad URL (Uniform Resource Locator). Usually the
client program gives an error message like:
Unable to connect to server
.
If the client can establish a connection to the server but gets no sensible response, you usually get an error message to that effect. This type of error is usually the hardest to diagnose and correct, unfortunately.
In this case the server sends a valid HTTP response to the request whose contents is a diagnostic error message rather than the intended information. When the server at Region 6 does this, the response contains a 1-line error description, prefaced with -ERROR-, and a dump of the failed request and header lines it received from the client. A link to a non-existent document, for example, will produce such an error.
Below are the common error messages generated by server with a description of their cause and possible corrective measures or workarounds.
no such file or directory
not owner
Access to object is _ruled_ out.
File _protected_ against access.
Syntax error or malformed request
Gateway function not available
invalid URL specified
Method not supported by this server
Search capability not enabled
Client does not accept data type