These constants are defined in the main cefpython module. They are for use with:
- LoadHandler.OnLoadError()
- WebRequestClient.OnError()
- RequestHandler.OnCertificateError()
For an up-to-date list of error codes see net_error_list.h in Chromium.
Table of contents:
- Constants
- ERR_NONE
- ERR_ABORTED
- ERR_ACCESS_DENIED
- ERR_ADDRESS_INVALID
- ERR_ADDRESS_UNREACHABLE
- ERR_CACHE_MISS
- ERR_CERT_AUTHORITY_INVALID
- ERR_CERT_COMMON_NAME_INVALID
- ERR_CERT_CONTAINS_ERRORS
- ERR_CERT_DATE_INVALID
- ERR_CERT_END
- ERR_CERT_INVALID
- ERR_CERT_NO_REVOCATION_MECHANISM
- ERR_CERT_REVOKED
- ERR_CERT_UNABLE_TO_CHECK_REVOCATION
- ERR_CONNECTION_ABORTED
- ERR_CONNECTION_CLOSED
- ERR_CONNECTION_FAILED
- ERR_CONNECTION_REFUSED
- ERR_CONNECTION_RESET
- ERR_DISALLOWED_URL_SCHEME
- ERR_EMPTY_RESPONSE
- ERR_FAILED
- ERR_FILE_NOT_FOUND
- ERR_FILE_TOO_BIG
- ERR_INSECURE_RESPONSE
- ERR_INTERNET_DISCONNECTED
- ERR_INVALID_ARGUMENT
- ERR_INVALID_CHUNKED_ENCODING
- ERR_INVALID_HANDLE
- ERR_INVALID_RESPONSE
- ERR_INVALID_URL
- ERR_METHOD_NOT_SUPPORTED
- ERR_NAME_NOT_RESOLVED
- ERR_NO_SSL_VERSIONS_ENABLED
- ERR_NOT_IMPLEMENTED
- ERR_RESPONSE_HEADERS_TOO_BIG
- ERR_SSL_CLIENT_AUTH_CERT_NEEDED
- ERR_SSL_PROTOCOL_ERROR
- ERR_SSL_RENEGOTIATION_REQUESTED
- ERR_SSL_VERSION_OR_CIPHER_MISMATCH
- ERR_TIMED_OUT
- ERR_TOO_MANY_REDIRECTS
- ERR_TUNNEL_CONNECTION_FAILED
- ERR_UNEXPECTED
- ERR_UNEXPECTED_PROXY_AUTH
- ERR_UNKNOWN_URL_SCHEME
- ERR_UNSAFE_PORT
- ERR_UNSAFE_REDIRECT
No error.
An operation was aborted (due to user action).
Permission to access a resource, other than the network, was denied.
The IP address or port number is invalid (e.g., cannot connect to the IP address 0 or the port 0).
The IP address is unreachable. This usually means that there is no route to the specified host or network.
The cache does not have the requested entry.
The server responded with a certificate that is signed by an authority we don't trust. That could mean:
- An attacker has substituted the real certificate for a cert that contains his public key and is signed by his cousin.
- The server operator has a legitimate certificate from a CA we don't know about, but should trust.
- The server is presenting a self-signed certificate, providing no defense against active attackers (but foiling passive attackers).
The server responded with a certificate whose common name did not match the host name. This could mean:
- An attacker has redirected our traffic to his server and is presenting a certificate for which he knows the private key.
- The server is misconfigured and responding with the wrong cert.
- The user is on a wireless network and is being redirected to the network's login page.
- The OS has used a DNS search suffix and the server doesn't have a certificate for the abbreviated name in the address bar.
The server responded with a certificate that contains errors. This error is not recoverable. MSDN describes this error as follows: "The SSL certificate contains errors." NOTE: It's unclear how this differs from ERR_CERT_INVALID. For consistency, use that code instead of this one from now on.
The server responded with a certificate that, by our clock, appears to either not yet be valid or to have expired. This could mean:
- An attacker is presenting an old certificate for which he has managed to obtain the private key.
- The server is misconfigured and is not presenting a valid cert.
- Our clock is wrong.
The value immediately past the last certificate error code.
The server responded with a certificate that is invalid. This error is not recoverable. MSDN describes this error as follows: "The SSL certificate is invalid."
The certificate has no mechanism for determining if it is revoked. In effect, this certificate cannot be revoked.
The server responded with a certificate has been revoked. We have the capability to ignore this error, but it is probably not the thing to do.
Revocation information for the security certificate for this site is not available. This could mean:
- An attacker has compromised the private key in the certificate and is blocking our attempt to find out that the cert was revoked.
- The certificate is unrevoked, but the revocation server is busy or unavailable.
A connection timed out as a result of not receiving an ACK for data sent. This can include a FIN packet that did not get ACK'd.
A connection was closed (corresponding to a TCP FIN).
A connection attempt failed.
A connection attempt was refused.
A connection was reset (corresponding to a TCP RST).
The scheme of the URL is disallowed.
The server closed the connection without sending any data.
A generic failure occurred.
The file or directory cannot be found.
The file is too large.
The server's response was insecure (e.g. there was a cert error).
The Internet connection has been lost.
An argument to the function is incorrect.
Error in chunked transfer encoding.
The handle or file descriptor is invalid.
The server's response was invalid.
The URL is invalid.
The server did not support the request method.
The host name could not be resolved.
No SSL protocol versions are enabled.
The operation failed because of unimplemented functionality.
The headers section of the response is too large.
The server requested a client certificate for SSL client authentication.
An SSL protocol error occurred.
The server requested a renegotiation (rehandshake).
The client and server don't support a common SSL protocol version or cipher suite.
An operation timed out.
Attempting to load an URL resulted in too many redirects.
A tunnel connection through the proxy could not be established.
An unexpected error. This may be caused by a programming mistake or an invalid assumption.
The response was 407 (Proxy Authentication Required), yet we did not send the request to a proxy.
The scheme of the URL is unknown.
Attempting to load an URL with an unsafe port number. These are port numbers that correspond to services, which are not robust to spurious input that may be constructed as a result of an allowed web construct (e.g., HTTP looks a lot like SMTP, so form submission to port 25 is denied).
Attempting to load an URL resulted in an unsafe redirect (e.g., a redirect to file:// is considered unsafe).