8xx No Connection

The 8xx status codes do not belong to the HTTP status codes defined in RFC 2616. They are part of the 200ok.eu status code extensions.

The 8xx class of status code is used when no valid response was received from the server. When this happens, 200ok.eu produces a diagnosis of the lack of response.

800 file: Scheme

The file: scheme can only be used to retrieve files from one’s own computer or local network.

806 Invalid Domain Name

The domain name is not valid.

807 Failed Connection

The domain name is valid, but the connection to the server failed.

818 Wrong File Size

The transfer was shorter or longer than expected. The server initially reported an expected transfer size, but the response did not match the given size.

828 Operation Timeout

The timeout period specified in 200ok.eu algorithms was reached and the connection was aborted by our software.

847 Too Many Redirects

When following redirections, our software reached the maximum number of redirects specified in 200ok.eu algorithms.

851 Peer failed verification

The server’s SSL certificate was deemed not okay.

852 No Answer

Nothing was returned from the server while a response was expected.

856 Reception Data Error

An error was detected in the reception of data from the server.

860 Not Authenticated With Known CA

Peer certificate cannot be authenticated with known CA certificates.

861 Bad Content Encoding

The content encoding in the server response was not recognized. The response did not match the supported encoding types specified in the Accept-Encoding header.

899 No Status Code

The server response header does not contain any HTTP status code.

Our technical forum Extended Status Codes (7xx-9xx) is available for questions and comments.