Enum Class NetError
- All Implemented Interfaces:
Serializable,Comparable<NetError>,Constable
-
Nested Class Summary
Nested classes/interfaces inherited from class java.lang.Enum
Enum.EnumDesc<E extends Enum<E>> -
Enum Constant Summary
Enum ConstantsEnum ConstantDescriptionAn operation was aborted due to user action.Permission to access a resource, other than the network, was denied.An error adding a certificate to the OS certificate database.Returned when attempting to bind an address that is already in use.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.The request to negotiate an alternate protocol failed.The SSL handshake failed because of a bad or missing client certificate.The request was blocked by the URL block list configured by the domain administrator.The client chose to block the request.The request failed because the response was delivered along with requirements which are not met (X-Frame-OptionsandContent-Security-Policyancestor checks andCross-Origin-Resource-Policy, for instance).Received a challenge after the transaction has read some data, and the credentials aren't available.The cache found an entry with an invalid checksum.The cache was unable to read a checksum record on an entry.The disk cache is unable to create this entry.The disk cache is unable to doom this entry.Internal not-quite error code for the HTTP cache.Internal error code for the HTTP cache.The cache does not have the requested entry.The disk cache is unable to open this entry.The disk cache is unable to open or create this entry.The operation is not supported for this entry.Multiple transactions are racing to create disk cache entries.Unable to read from the disk cache.Unable to write to the disk cache.The server responded with a certificate that is signed by an authority we don't trust.The server responded with a certificate whose common name did not match the host name.The server responded with a certificate that contains errors.The certificate database changed in some way.The server responded with a certificate that, by our clock, appears to either not yet be valid or to have expired.The value immediately past the last certificate error code.The server responded with a certificate that is invalid.The certificate claimed DNS names that are in violation of name constraints.The certificate has no mechanism for determining if it is revoked.The host name specified in the certificate is not unique.The server responded with a certificate that has been revoked.Certificate Transparency was required for this connection, but the server did not provide CT information that complied with the policy.Revocation information for the security certificate for this site is not available.The certificate's validity period is too long.The server responded with a certificate that contains a weak key (e.g.The server responded with a certificate that is signed using a weak signature algorithm.Server request for client certificate did not contain any types we support.A connection timed out as a result of not receiving an ACK for data sent.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).A connection attempt timed out.Content decoding of the response body failed.Initializing content decoding failed.The HTTP response body transferred fewer bytes than were advertised by theContent-Lengthheader when the connection is closed.The request failed because theURLRequestContextis shutting down, or has been shut down.Certificate Transparency: Failed to parse the received consistency proof.Certificate Transparency: Received a signed tree head whose JSON parsing was OK but was missing some of the fields.Certificate Transparency: Received a signed tree head that failed to parse.The scheme of the URL is disallowed.The entry was not found in cache or other local sources, for lookups where only local sources were queried.DNS resolver received a malformed response.Suffix search list rules prevent resolution of the given host name.DNS server failed.DNS server requires TCP.Failed to sort addresses according to RFC3484.DNS transaction timed out.TLS 1.3 early data was rejected by the server.The server closed the connection without sending any data.Detecting the encoding of the response failed.A generic failure occurred.The file already exists.Not enough room left on the disk.The file or directory cannot be found.The path or file name is too long.The file is too large.The file has a virus.There are too many pending DNS resolves, so a request in the queue was aborted.HTTP_1_1_REQUIREDerror code received on HTTP/2 session.The server returned a non-2xx HTTP response code.Decoding or encoding of compressed HTTP/2 headers failed.The peer violated HTTP/2 flow control.The peer sent an improperly sized HTTP/2 frame.Transport security is inadequate for the HTTP/2 version.HTTP/2 server didn't respond to thePINGmessage.There is an HTTP/2 protocol error.Received HTTP/2RST_STREAMframe withNO_ERRORerror code.HTTP/2 server refused the request without processing, and sent either aGOAWAYframe with error codeNO_ERRORandLast-Stream-IDlower than the stream id corresponding to the request indicating that this request has not been processed yet, or aRST_STREAMframe with error codeREFUSED_STREAM.Received an HTTP/2 frame on a closed stream.Resolving a hostname to an IP address list included the IPv4 address127.0.53.53.CA import failed due to some other error.CA import failed - not a CA cert.Import failed, a certificate already exists in database.Server certificate import failed due to some internal error.The HTTP response body is transferred withChunked-Encoding, but the terminating zero-length chunk was never sent when the connection is closed.HTTP/2 headers have been received, but not all of them — status or version headers are missing, so we're expecting additional frames to complete them.The server's response was insecure, e.g.There were not enough resources to complete the operation.The Internet connection has been lost.An argument to the function is incorrect.Credentials could not be established during HTTP Authentication.Error in chunked transfer encoding.The handle or file descriptor is invalid.The server was expected to return an HTTP/1.x response, but did not.Attempting to load a URL resulted in a redirect to an invalid URL.The server's response was invalid.An error occurred while handling a signed exchange.The URL is invalid.An error occurred while handling a Web Bundle source.An asynchronous IO operation is not yet complete.Key generation failed.The identity used for authentication is invalid.A mandatory proxy configuration could not be used.The server did not support the request method.The environment was not set up correctly for authentication (for example, no KDC could be found or the principal is unknown).No Kerberos credentials were available during HTTP Authentication.The message was too large for the transport.The host name could not be resolved.An error occurred when trying to do a name resolution (DNS).Permission to access the network was denied.The network changed.An operation could not be completed because all network IO is suspended.No socket buffer space is available.An attempt to import a client certificate failed, as the user's key database lacked a corresponding private key.There are no supported proxies in the provided list.The operation failed because of unimplemented functionality.No error.Memory allocation failed.No PAC URL configuration could be retrieved from DHCP.The evaluation of the PAC script failed.The PAC script terminated fatally and must be reloaded.PKCS #12 import failed due to incorrect password.PKCS #12 import failed due to other error.PKCS #12 import failed due to invalid/corrupt file.PKCS #12 import failed due to invalid MAC.PKCS #12 import failed due to unsupported features.The max socket limit for the socket pool has been hit while pre-connecting.Failure to export private key.The proxy requested authentication for tunnel establishment.Proxy authentication requested without a valid client socket handle.The proxy requested authentication (for tunnel establishment) with an unsupported method.The certificate presented by the HTTPS Proxy was invalid.A failure to create a connection to the proxy server.HTTP_1_1_REQUIREDerror code received on HTTP/2 session to proxy.The certificate presented on a QUIC connection does not chain to a known root and the origin connected to is not on a list of domains where unknown roots are allowed.The QUIC crypto handshake failed.There is a QUIC protocol error.SocketReadIfReadysupport is not implemented.The response was 416 (Requested range not satisfiable) and the server cannot satisfy the range requested.The HTTP response was too big to drain.The HTTP response contained multiple Content-Disposition headers.The HTTP response contained multiple distinct Content-Length headers.The HTTP response contained multiple Location headers.The headers section of the response is too large.The HTTP headers were truncated by an EOF.Self-signed certificate generation failed.The socket is already connected.The socket is not connected.Failed to set the socket's receive buffer size as requested, despite success return code fromsetsockopt.Failed to set the socket's send buffer size as requested, despite success return code fromsetsockopt.Failed to set the socket's receive buffer size as requested.Failed to set the socket's send buffer size as requested.Failed establishing a connection to the SOCKS proxy server for a target host.The SOCKS proxy server failed establishing connection to the target host because that host is unreachable.An SSL peer sent us a fatalbad_record_macalert.Failed to import a client certificate from the platform store into the SSL library.The server requested a client certificate for SSL client authentication.The SSL client certificate has no private key.There were no common signature algorithms between our client certificate private key and the server's preferences.The permission to use the SSL client certificate's private key was denied.We were unable to sign the CertificateVerify data of an SSL client auth handshake with the client certificate's private key.An SSL peer sent us a fataldecompression_failurealert.An SSL peer sent us a fataldecrypt_erroralert.The server's certificate has a keyUsage extension incompatible with the negotiated TLS key exchange method.The peer sent an SSL no_renegotiation alert message.The SSL server required an unsupported cipher suite that has since been removed.The certificate didn't match the built-in public key pins for the host name.An SSL protocol error occurred.The server requested a renegotiation (rehandshake).The SSL server presented a certificate which could not be decoded.The SSL server certificate changed in a renegotiation.The SSL server sent us a fatal unrecognized_name alert.The client and server don't support a common SSL protocol version or cipher suite.The request throttler module cancelled this request to avoid DDOS.An operation timed out.TLS 1.3 was enabled, but a lower version was negotiated and the server returned a value indicating it supported TLS 1.3.Attempting to load a URL resulted in too many redirects.An HTTP transaction was retried too many times due for authentication or invalid certificates.When handling a Trust Tokens protocol operation-executing request, the system found that the request's desired Trust Tokens results were already present in a local cache; as a result, the main request was cancelled.A Trust Tokens protocol operation-executing request failed for one of a number of reasons (precondition failure, internal error, bad response).A tunnel connection through the proxy could not be established.The attempt to reuse a connection to send proxy auth credentials failed before theAuthControllerwas used to generate credentials.An undocumented SSPI or GSSAPI status code was returned.An unexpected error.The response was 407 (Proxy Authentication Required), yet we did not send the request to a proxy.An unexpected, but documented, SSPI or GSSAPI status code was returned.The error is unknown.The scheme of the URL is unknown.Attempting to load a URL with an unsafe port number.Attempting to load a URL resulted in an unsafe redirect (e.g., a redirect tofile://is considered unsafe).An HTTP Authentication scheme was tried which is not supported on this machine.The file upload failed because the file's modification time was different from the expectation.The upload failed because the upload stream needed to be re-read, due to a retry or a redirect, but the upload stream doesn't support that operation.Winsock sometimes reports more data written than passed.TLS 1.3 early data was offered, but the server responded with TLS 1.2 or earlier.Websocket protocol error.There are too many pendingWebSocketJobinstances, so the new job was not pushed to the queue.When a WebSocket handshake is done successfully and the connection has been upgraded, theURLRequestis cancelled with this error code. -
Method Summary
Methods inherited from class java.lang.Enum
compareTo, describeConstable, equals, getDeclaringClass, hashCode, name, ordinal, toString, valueOf
-
Enum Constant Details
-
UNKNOWN
The error is unknown. -
OK
No error. -
IO_PENDING
An asynchronous IO operation is not yet complete. This usually does not indicate a fatal error.Typically, this error will be generated as a notification to wait for some external notification that the IO operation finally completed.
-
FAILED
A generic failure occurred. -
ABORTED
An operation was aborted due to user action. -
INVALID_ARGUMENT
An argument to the function is incorrect. -
INVALID_HANDLE
The handle or file descriptor is invalid. -
FILE_NOT_FOUND
The file or directory cannot be found. -
TIMED_OUT
An operation timed out. -
FILE_TOO_BIG
The file is too large. -
UNEXPECTED
An unexpected error. This may be caused by a programming mistake or an invalid assumption. -
ACCESS_DENIED
Permission to access a resource, other than the network, was denied. -
NOT_IMPLEMENTED
The operation failed because of unimplemented functionality. -
INSUFFICIENT_RESOURCES
There were not enough resources to complete the operation. -
OUT_OF_MEMORY
Memory allocation failed. -
UPLOAD_FILE_CHANGED
The file upload failed because the file's modification time was different from the expectation. -
SOCKET_NOT_CONNECTED
The socket is not connected. -
FILE_EXISTS
The file already exists. -
FILE_PATH_TOO_LONG
The path or file name is too long. -
FILE_NO_SPACE
Not enough room left on the disk. -
FILE_VIRUS_INFECTED
The file has a virus. -
BLOCKED_BY_CLIENT
The client chose to block the request. -
NETWORK_CHANGED
The network changed. -
BLOCKED_BY_ADMINISTRATOR
The request was blocked by the URL block list configured by the domain administrator. -
SOCKET_IS_CONNECTED
The socket is already connected. -
UPLOAD_STREAM_REWIND_NOT_SUPPORTED
The upload failed because the upload stream needed to be re-read, due to a retry or a redirect, but the upload stream doesn't support that operation. -
CONTEXT_SHUT_DOWN
The request failed because theURLRequestContextis shutting down, or has been shut down. -
BLOCKED_BY_RESPONSE
The request failed because the response was delivered along with requirements which are not met (X-Frame-OptionsandContent-Security-Policyancestor checks andCross-Origin-Resource-Policy, for instance). -
CONNECTION_CLOSED
A connection was closed (corresponding to a TCP FIN). -
CONNECTION_RESET
A connection was reset (corresponding to a TCP RST). -
CONNECTION_REFUSED
A connection attempt was refused. -
CONNECTION_ABORTED
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. -
CONNECTION_FAILED
A connection attempt failed. -
NAME_NOT_RESOLVED
The host name could not be resolved. -
INTERNET_DISCONNECTED
The Internet connection has been lost. -
SSL_PROTOCOL_ERROR
An SSL protocol error occurred. -
ADDRESS_INVALID
The IP address or port number is invalid (e.g., cannot connect to the IP address 0 or the port 0). -
ADDRESS_UNREACHABLE
The IP address is unreachable. This usually means that there is no route to the specified host or network. -
SSL_CLIENT_AUTH_CERT_NEEDED
The server requested a client certificate for SSL client authentication. -
TUNNEL_CONNECTION_FAILED
A tunnel connection through the proxy could not be established. -
SSL_VERSION_OR_CIPHER_MISMATCH
The client and server don't support a common SSL protocol version or cipher suite. -
SSL_RENEGOTIATION_REQUESTED
The server requested a renegotiation (rehandshake). -
PROXY_AUTH_UNSUPPORTED
The proxy requested authentication (for tunnel establishment) with an unsupported method. -
BAD_SSL_CLIENT_AUTH_CERT
The SSL handshake failed because of a bad or missing client certificate. -
CONNECTION_TIMED_OUT
A connection attempt timed out. -
HOST_RESOLVER_QUEUE_TOO_LARGE
There are too many pending DNS resolves, so a request in the queue was aborted. -
SOCKS_CONNECTION_FAILED
Failed establishing a connection to the SOCKS proxy server for a target host. -
SOCKS_CONNECTION_HOST_UNREACHABLE
The SOCKS proxy server failed establishing connection to the target host because that host is unreachable. -
ALPN_NEGOTIATION_FAILED
The request to negotiate an alternate protocol failed. -
SSL_NO_RENEGOTIATION
The peer sent an SSL no_renegotiation alert message. -
WINSOCK_UNEXPECTED_WRITTEN_BYTES
Winsock sometimes reports more data written than passed. This can be due to a broken LSP. -
SSL_DECOMPRESSION_FAILURE_ALERT
An SSL peer sent us a fataldecompression_failurealert. This typically occurs when a peer selectsDEFLATEcompression in the mistaken belief that it supports it. -
SSL_BAD_RECORD_MAC_ALERT
An SSL peer sent us a fatalbad_record_macalert. This has been observed from servers with buggyDEFLATEsupport. -
PROXY_AUTH_REQUESTED
The proxy requested authentication for tunnel establishment. -
PROXY_CONNECTION_FAILED
A failure to create a connection to the proxy server.An error occurred either in resolving the server's name, or in connecting a socket to it.
This does NOT include failures during the actual
CONNECTmethod of an HTTP proxy. -
MANDATORY_PROXY_CONFIGURATION_FAILED
A mandatory proxy configuration could not be used. Currently, this means that a mandatory PAC script could not be fetched, parsed or executed. -
PRECONNECT_MAX_SOCKET_LIMIT
The max socket limit for the socket pool has been hit while pre-connecting. The library doesn't bother trying to pre-connect more sockets. -
SSL_CLIENT_AUTH_PRIVATE_KEY_ACCESS_DENIED
The permission to use the SSL client certificate's private key was denied. -
SSL_CLIENT_AUTH_CERT_NO_PRIVATE_KEY
The SSL client certificate has no private key. -
PROXY_CERTIFICATE_INVALID
The certificate presented by the HTTPS Proxy was invalid. -
NAME_RESOLUTION_FAILED
An error occurred when trying to do a name resolution (DNS). -
NETWORK_ACCESS_DENIED
Permission to access the network was denied. This is used to distinguish errors that were most likely caused by a firewall from other access denied errors. -
TEMPORARILY_THROTTLED
The request throttler module cancelled this request to avoid DDOS. -
SSL_CLIENT_AUTH_SIGNATURE_FAILED
We were unable to sign the CertificateVerify data of an SSL client auth handshake with the client certificate's private key.Possible causes for this include the user implicitly or explicitly denying access to the private key, the private key may not be valid for signing, the key may be relying on a cached handle which is no longer valid, or the CSP won't allow arbitrary data to be signed.
-
MSG_TOO_BIG
The message was too large for the transport. For example, a UDP message which exceeds size threshold. -
WS_PROTOCOL_ERROR
Websocket protocol error. Indicates that we are terminating the connection due to a malformed frame or other protocol violation. -
ADDRESS_IN_USE
Returned when attempting to bind an address that is already in use. -
SSL_PINNED_KEY_NOT_IN_CERT_CHAIN
The certificate didn't match the built-in public key pins for the host name. -
CLIENT_AUTH_CERT_TYPE_UNSUPPORTED
Server request for client certificate did not contain any types we support. -
SSL_DECRYPT_ERROR_ALERT
An SSL peer sent us a fataldecrypt_erroralert. This typically occurs when a peer could not correctly verify a signature (inCertificateVerifyorServerKeyExchange) or validate aFinishedmessage. -
WS_THROTTLE_QUEUE_TOO_LARGE
There are too many pendingWebSocketJobinstances, so the new job was not pushed to the queue. -
SSL_SERVER_CERT_CHANGED
The SSL server certificate changed in a renegotiation. -
SSL_UNRECOGNIZED_NAME_ALERT
The SSL server sent us a fatal unrecognized_name alert. -
SOCKET_SET_RECEIVE_BUFFER_SIZE_ERROR
Failed to set the socket's receive buffer size as requested. -
SOCKET_SET_SEND_BUFFER_SIZE_ERROR
Failed to set the socket's send buffer size as requested. -
SOCKET_RECEIVE_BUFFER_SIZE_UNCHANGEABLE
Failed to set the socket's receive buffer size as requested, despite success return code fromsetsockopt. -
SOCKET_SEND_BUFFER_SIZE_UNCHANGEABLE
Failed to set the socket's send buffer size as requested, despite success return code fromsetsockopt. -
SSL_CLIENT_AUTH_CERT_BAD_FORMAT
Failed to import a client certificate from the platform store into the SSL library. -
ICANN_NAME_COLLISION
Resolving a hostname to an IP address list included the IPv4 address127.0.53.53. This is a special IP address which ICANN has recommended to indicate there was a name collision, and alert admins to a potential problem. -
SSL_SERVER_CERT_BAD_FORMAT
The SSL server presented a certificate which could not be decoded. This is not a certificate error code as noX509Certificateobject is available. This error is fatal. -
CT_STH_PARSING_FAILED
Certificate Transparency: Received a signed tree head that failed to parse. -
CT_STH_INCOMPLETE
Certificate Transparency: Received a signed tree head whose JSON parsing was OK but was missing some of the fields. -
UNABLE_TO_REUSE_CONNECTION_FOR_PROXY_AUTH
The attempt to reuse a connection to send proxy auth credentials failed before theAuthControllerwas used to generate credentials. The caller should reuse the controller with a new connection. This error is only used internally by the network stack. -
CT_CONSISTENCY_PROOF_PARSING_FAILED
Certificate Transparency: Failed to parse the received consistency proof. -
SSL_OBSOLETE_CIPHER
The SSL server required an unsupported cipher suite that has since been removed. This error will temporarily be signaled on a fallback for one or two releases immediately following a cipher suite's removal, after which the fallback will be removed. -
WS_UPGRADE
When a WebSocket handshake is done successfully and the connection has been upgraded, theURLRequestis cancelled with this error code. -
READ_IF_READY_NOT_IMPLEMENTED
SocketReadIfReadysupport is not implemented. This error should not be user visible, because the normalReadmethod is used as a fallback. -
NO_BUFFER_SPACE
No socket buffer space is available. -
SSL_CLIENT_AUTH_NO_COMMON_ALGORITHMS
There were no common signature algorithms between our client certificate private key and the server's preferences. -
EARLY_DATA_REJECTED
TLS 1.3 early data was rejected by the server. This will be received before any data is returned from the socket. The request should be retried with early data disabled. -
WRONG_VERSION_ON_EARLY_DATA
TLS 1.3 early data was offered, but the server responded with TLS 1.2 or earlier. This is an internal error code to account for a backwards-compatibility issue with early data and TLS 1.2. It will be received before any data is returned from the socket. The request should be retried with early data disabled.See here for details.
-
TLS13_DOWNGRADE_DETECTED
TLS 1.3 was enabled, but a lower version was negotiated and the server returned a value indicating it supported TLS 1.3. This is part of a security check in TLS 1.3, but it may also indicate the user is behind a buggy TLS-terminating proxy which implemented TLS 1.2 incorrectly. -
SSL_KEY_USAGE_INCOMPATIBLE
The server's certificate has a keyUsage extension incompatible with the negotiated TLS key exchange method. -
CERT_COMMON_NAME_INVALID
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.
-
CERT_DATE_INVALID
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.
-
CERT_AUTHORITY_INVALID
The server responded with a certificate that is signed by an authority we don't trust. This 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).
-
CERT_CONTAINS_ERRORS
The server responded with a certificate that contains errors. This error is not recoverable. -
CERT_NO_REVOCATION_MECHANISM
The certificate has no mechanism for determining if it is revoked. In effect, this certificate cannot be revoked. -
CERT_UNABLE_TO_CHECK_REVOCATION
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 not revoked, but the revocation server is busy or unavailable.
-
CERT_REVOKED
The server responded with a certificate that has been revoked. -
CERT_INVALID
The server responded with a certificate that is invalid. This error is not recoverable. -
CERT_WEAK_SIGNATURE_ALGORITHM
The server responded with a certificate that is signed using a weak signature algorithm. -
CERT_NON_UNIQUE_NAME
The host name specified in the certificate is not unique. -
CERT_WEAK_KEY
The server responded with a certificate that contains a weak key (e.g. a too-small RSA key). -
CERT_NAME_CONSTRAINT_VIOLATION
The certificate claimed DNS names that are in violation of name constraints. -
CERT_VALIDITY_TOO_LONG
The certificate's validity period is too long. -
CERT_TRANSPARENCY_REQUIRED
Certificate Transparency was required for this connection, but the server did not provide CT information that complied with the policy. -
CERT_END
The value immediately past the last certificate error code. -
INVALID_URL
The URL is invalid. -
DISALLOWED_URL_SCHEME
The scheme of the URL is disallowed. -
UNKNOWN_URL_SCHEME
The scheme of the URL is unknown. -
INVALID_REDIRECT
Attempting to load a URL resulted in a redirect to an invalid URL. -
TOO_MANY_REDIRECTS
Attempting to load a URL resulted in too many redirects. -
UNSAFE_REDIRECT
Attempting to load a URL resulted in an unsafe redirect (e.g., a redirect tofile://is considered unsafe). -
UNSAFE_PORT
Attempting to load a 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). -
INVALID_RESPONSE
The server's response was invalid. -
INVALID_CHUNKED_ENCODING
Error in chunked transfer encoding. -
METHOD_NOT_SUPPORTED
The server did not support the request method. -
UNEXPECTED_PROXY_AUTH
The response was 407 (Proxy Authentication Required), yet we did not send the request to a proxy. -
EMPTY_RESPONSE
The server closed the connection without sending any data. -
RESPONSE_HEADERS_TOO_BIG
The headers section of the response is too large. -
PAC_SCRIPT_FAILED
The evaluation of the PAC script failed. -
REQUEST_RANGE_NOT_SATISFIABLE
The response was 416 (Requested range not satisfiable) and the server cannot satisfy the range requested. -
MALFORMED_IDENTITY
The identity used for authentication is invalid. -
CONTENT_DECODING_FAILED
Content decoding of the response body failed. -
NETWORK_IO_SUSPENDED
An operation could not be completed because all network IO is suspended. -
NO_SUPPORTED_PROXIES
There are no supported proxies in the provided list. -
HTTP2_PROTOCOL_ERROR
There is an HTTP/2 protocol error. -
INVALID_AUTH_CREDENTIALS
Credentials could not be established during HTTP Authentication. -
UNSUPPORTED_AUTH_SCHEME
An HTTP Authentication scheme was tried which is not supported on this machine. -
ENCODING_DETECTION_FAILED
Detecting the encoding of the response failed. -
MISSING_AUTH_CREDENTIALS
No Kerberos credentials were available during HTTP Authentication. -
UNEXPECTED_SECURITY_LIBRARY_STATUS
An unexpected, but documented, SSPI or GSSAPI status code was returned. -
MISCONFIGURED_AUTH_ENVIRONMENT
The environment was not set up correctly for authentication (for example, no KDC could be found or the principal is unknown). -
UNDOCUMENTED_SECURITY_LIBRARY_STATUS
An undocumented SSPI or GSSAPI status code was returned. -
RESPONSE_BODY_TOO_BIG_TO_DRAIN
The HTTP response was too big to drain. -
RESPONSE_HEADERS_MULTIPLE_CONTENT_LENGTH
The HTTP response contained multiple distinct Content-Length headers. -
INCOMPLETE_HTTP2_HEADERS
HTTP/2 headers have been received, but not all of them — status or version headers are missing, so we're expecting additional frames to complete them. -
PAC_NOT_IN_DHCP
No PAC URL configuration could be retrieved from DHCP. This can indicate either a failure to retrieve the DHCP configuration, or that there was no PAC URL configured in DHCP. -
RESPONSE_HEADERS_MULTIPLE_CONTENT_DISPOSITION
The HTTP response contained multiple Content-Disposition headers. -
RESPONSE_HEADERS_MULTIPLE_LOCATION
The HTTP response contained multiple Location headers. -
HTTP2_SERVER_REFUSED_STREAM
HTTP/2 server refused the request without processing, and sent either aGOAWAYframe with error codeNO_ERRORandLast-Stream-IDlower than the stream id corresponding to the request indicating that this request has not been processed yet, or aRST_STREAMframe with error codeREFUSED_STREAM. -
HTTP2_PING_FAILED
HTTP/2 server didn't respond to thePINGmessage. -
CONTENT_LENGTH_MISMATCH
The HTTP response body transferred fewer bytes than were advertised by theContent-Lengthheader when the connection is closed. -
INCOMPLETE_CHUNKED_ENCODING
The HTTP response body is transferred withChunked-Encoding, but the terminating zero-length chunk was never sent when the connection is closed. -
QUIC_PROTOCOL_ERROR
There is a QUIC protocol error. -
RESPONSE_HEADERS_TRUNCATED
The HTTP headers were truncated by an EOF. -
QUIC_HANDSHAKE_FAILED
The QUIC crypto handshake failed. This means that the server was unable to read any requests sent, so they may be resent. -
HTTP2_INADEQUATE_TRANSPORT_SECURITY
Transport security is inadequate for the HTTP/2 version. -
HTTP2_FLOW_CONTROL_ERROR
The peer violated HTTP/2 flow control. -
HTTP2_FRAME_SIZE_ERROR
The peer sent an improperly sized HTTP/2 frame. -
HTTP2_COMPRESSION_ERROR
Decoding or encoding of compressed HTTP/2 headers failed. -
PROXY_AUTH_REQUESTED_WITH_NO_CONNECTION
Proxy authentication requested without a valid client socket handle. -
HTTP_1_1_REQUIRED
HTTP_1_1_REQUIREDerror code received on HTTP/2 session. -
PROXY_HTTP_1_1_REQUIRED
HTTP_1_1_REQUIREDerror code received on HTTP/2 session to proxy. -
PAC_SCRIPT_TERMINATED
The PAC script terminated fatally and must be reloaded. -
INVALID_HTTP_RESPONSE
The server was expected to return an HTTP/1.x response, but did not. Rather than treat it as HTTP/0.9, this error is returned. -
CONTENT_DECODING_INIT_FAILED
Initializing content decoding failed. -
HTTP2_RST_STREAM_NO_ERROR_RECEIVED
Received HTTP/2RST_STREAMframe withNO_ERRORerror code. This error should be handled internally by HTTP/2 code, and should not make it above theSpdyStreamlayer. -
TOO_MANY_RETRIES
An HTTP transaction was retried too many times due for authentication or invalid certificates. This may be due to a bug in the net stack that would otherwise infinite loop, or if the server or proxy continually requests fresh credentials or presents a fresh invalid certificate. -
HTTP2_STREAM_CLOSED
Received an HTTP/2 frame on a closed stream. -
HTTP_RESPONSE_CODE_FAILURE
The server returned a non-2xx HTTP response code.Note that this error is only used by certain APIs that interpret the HTTP response itself.
URLRequestfor instance just passes most non-2xx response back as success. -
QUIC_CERT_ROOT_NOT_KNOWN
The certificate presented on a QUIC connection does not chain to a known root and the origin connected to is not on a list of domains where unknown roots are allowed. -
CACHE_MISS
The cache does not have the requested entry. -
CACHE_READ_FAILURE
Unable to read from the disk cache. -
CACHE_WRITE_FAILURE
Unable to write to the disk cache. -
CACHE_OPERATION_NOT_SUPPORTED
The operation is not supported for this entry. -
CACHE_OPEN_FAILURE
The disk cache is unable to open this entry. -
CACHE_CREATE_FAILURE
The disk cache is unable to create this entry. -
CACHE_RACE
Multiple transactions are racing to create disk cache entries. This is an internal error returned from theHttpCacheto theHttpCacheTransactionthat tells the transaction to restart the entry-creation logic because the state of the cache has changed. -
CACHE_CHECKSUM_READ_FAILURE
The cache was unable to read a checksum record on an entry. This can be returned from attempts to read from the cache. It is an internal error, returned by theSimpleCachebackend, but not by anyURLRequestmethods or members. -
CACHE_CHECKSUM_MISMATCH
The cache found an entry with an invalid checksum. This can be returned from attempts to read from the cache. It is an internal error, returned by theSimpleCachebackend, but not by anyURLRequestmethods or members. -
CACHE_LOCK_TIMEOUT
Internal error code for the HTTP cache. The cache lock timeout has fired. -
CACHE_AUTH_FAILURE_AFTER_READ
Received a challenge after the transaction has read some data, and the credentials aren't available. There isn't a way to get them at that point. -
CACHE_ENTRY_NOT_SUITABLE
Internal not-quite error code for the HTTP cache. In-memory hints suggest that the cache entry would not have been usable with the transaction's current configuration, e.g. load flags, mode, etc. -
CACHE_DOOM_FAILURE
The disk cache is unable to doom this entry. -
CACHE_OPEN_OR_CREATE_FAILURE
The disk cache is unable to open or create this entry. -
INSECURE_RESPONSE
The server's response was insecure, e.g. there was a cert error. -
NO_PRIVATE_KEY_FOR_CERT
An attempt to import a client certificate failed, as the user's key database lacked a corresponding private key. -
ADD_USER_CERT_FAILED
An error adding a certificate to the OS certificate database. -
INVALID_SIGNED_EXCHANGE
An error occurred while handling a signed exchange. -
INVALID_WEB_BUNDLE
An error occurred while handling a Web Bundle source. -
TRUST_TOKEN_OPERATION_FAILED
A Trust Tokens protocol operation-executing request failed for one of a number of reasons (precondition failure, internal error, bad response). -
TRUST_TOKEN_OPERATION_CACHE_HIT
When handling a Trust Tokens protocol operation-executing request, the system found that the request's desired Trust Tokens results were already present in a local cache; as a result, the main request was cancelled. -
PKCS12_IMPORT_BAD_PASSWORD
PKCS #12 import failed due to incorrect password. -
PKCS12_IMPORT_FAILED
PKCS #12 import failed due to other error. -
IMPORT_CA_CERT_NOT_CA
CA import failed - not a CA cert. -
IMPORT_CERT_ALREADY_EXISTS
Import failed, a certificate already exists in database. -
IMPORT_CA_CERT_FAILED
CA import failed due to some other error. -
IMPORT_SERVER_CERT_FAILED
Server certificate import failed due to some internal error. -
PKCS12_IMPORT_INVALID_MAC
PKCS #12 import failed due to invalid MAC. -
PKCS12_IMPORT_INVALID_FILE
PKCS #12 import failed due to invalid/corrupt file. -
PKCS12_IMPORT_UNSUPPORTED
PKCS #12 import failed due to unsupported features. -
KEY_GENERATION_FAILED
Key generation failed. -
PRIVATE_KEY_EXPORT_FAILED
Failure to export private key. -
SELF_SIGNED_CERT_GENERATION_FAILED
Self-signed certificate generation failed. -
CERT_DATABASE_CHANGED
The certificate database changed in some way. -
DNS_MALFORMED_RESPONSE
DNS resolver received a malformed response. -
DNS_SERVER_REQUIRES_TCP
DNS server requires TCP. -
DNS_SERVER_FAILED
DNS server failed. This error is returned for all the following error conditions:- Format error - The name server was unable to interpret the query.
- Server failure - The name server was unable to process this query due to a problem with the name server.
- Not Implemented - The name server does not support the requested kind of query.
- Refused - The name server refuses to perform the specified operation for policy reasons.
-
DNS_TIMED_OUT
DNS transaction timed out. -
DNS_CACHE_MISS
The entry was not found in cache or other local sources, for lookups where only local sources were queried. -
DNS_SEARCH_EMPTY
Suffix search list rules prevent resolution of the given host name. -
DNS_SORT_ERROR
Failed to sort addresses according to RFC3484.
-
-
Method Details
-
values
Returns an array containing the constants of this enum class, in the order they are declared.- Returns:
- an array containing the constants of this enum class, in the order they are declared
-
valueOf
Returns the enum constant of this class with the specified name. The string must match exactly an identifier used to declare an enum constant in this class. (Extraneous whitespace characters are not permitted.)- Parameters:
name- the name of the enum constant to be returned.- Returns:
- the enum constant with the specified name
- Throws:
IllegalArgumentException- if this enum class has no constant with the specified nameNullPointerException- if the argument is null
-