Chromium Code Reviews| Index: mojo/services/network/public/interfaces/network_error.mojom |
| diff --git a/mojo/services/network/public/interfaces/network_error.mojom b/mojo/services/network/public/interfaces/network_error.mojom |
| index 8c2294850e790ffdcf601ab767413b6a6b5f08e0..2c2d13d63b39b54f5972e7678a66b090c02c689c 100644 |
| --- a/mojo/services/network/public/interfaces/network_error.mojom |
| +++ b/mojo/services/network/public/interfaces/network_error.mojom |
| @@ -5,6 +5,336 @@ |
| module mojo; |
| struct NetworkError { |
| - int32 code; |
| + NetworkCode code; |
| string? description; |
| }; |
| + |
| +// Corresponds to net/base/net_error_list.h. |
|
jamesr
2015/02/18 18:43:06
this isn't a helpful comment in the mojom as consu
ppi
2015/02/19 14:22:18
Done.
|
| +enum NetworkCode { |
| + OK = 0, |
| + |
| + // 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. |
| + IO_PENDING = -1, |
| + |
| + // A generic failure occurred. |
| + FAILED = -2, |
| + |
| + // An operation was aborted (due to user action). |
| + ABORTED = -3, |
| + |
| + // An argument to the function is incorrect. |
| + INVALID_ARGUMENT = -4, |
| + |
| + // The handle or file descriptor is invalid. |
| + INVALID_HANDLE = -5, |
| + |
| + // The file or directory cannot be found. |
| + FILE_NOT_FOUND = -6, |
| + |
| + // An operation timed out. |
| + TIMED_OUT = -7, |
| + |
| + // The file is too large. |
| + FILE_TOO_BIG = -8, |
| + |
| + // An unexpected error. This may be caused by a programming mistake or an |
| + // invalid assumption. |
| + UNEXPECTED = -9, |
| + |
| + // Permission to access a resource, other than the network, was denied. |
| + ACCESS_DENIED = -10, |
| + |
| + // The operation failed because of unimplemented functionality. |
| + NOT_IMPLEMENTED = -11, |
| + |
| + // There were not enough resources to complete the operation. |
| + INSUFFICIENT_RESOURCES = -12, |
| + |
| + // Memory allocation failed. |
| + OUT_OF_MEMORY = -13, |
| + |
| + // The file upload failed because the file's modification time was different |
| + // from the expectation. |
| + UPLOAD_FILE_CHANGED = -14, |
| + |
| + // The socket is not connected. |
| + SOCKET_NOT_CONNECTED = -15, |
| + |
| + // The file already exists. |
| + FILE_EXISTS = -16, |
| + |
| + // The path or file name is too long. |
| + FILE_PATH_TOO_LONG = -17, |
| + |
| + // Not enough room left on the disk. |
| + FILE_NO_SPACE = -18, |
| + |
| + // The file has a virus. |
| + FILE_VIRUS_INFECTED = -19, |
| + |
| + // The client chose to block the request. |
| + BLOCKED_BY_CLIENT = -20, |
| + |
| + // The network changed. |
| + NETWORK_CHANGED = -21, |
| + |
| + // The request was blocked by the URL blacklist configured by the domain |
| + // administrator. |
| + BLOCKED_BY_ADMINISTRATOR = -22, |
| + |
| + // The socket is already connected. |
| + SOCKET_IS_CONNECTED = -23, |
| + |
| + // The request was blocked because the forced reenrollment check is still |
| + // pending. This error can only occur on ChromeOS. The error can be emitted by |
| + // code in chrome/browser/policy/policy_helpers.cc. |
| + BLOCKED_ENROLLMENT_CHECK_PENDING = -24, |
| + |
| + // 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. |
| + UPLOAD_STREAM_REWIND_NOT_SUPPORTED = -25, |
| + |
| + // A connection was closed (corresponding to a TCP FIN). |
| + CONNECTION_CLOSED = -100, |
| + |
| + // A connection was reset (corresponding to a TCP RST). |
| + CONNECTION_RESET = -101, |
| + |
| + // A connection attempt was refused. |
| + CONNECTION_REFUSED = -102, |
| + |
| + // 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_ABORTED = -103, |
| + |
| + // A connection attempt failed. |
| + CONNECTION_FAILED = -104, |
| + |
| + // The host name could not be resolved. |
| + NAME_NOT_RESOLVED = -105, |
| + |
| + // The Internet connection has been lost. |
| + INTERNET_DISCONNECTED = -106, |
| + |
| + // An SSL protocol error occurred. |
| + SSL_PROTOCOL_ERROR = -107, |
| + |
| + // The IP address or port number is invalid (e.g., cannot connect to the IP |
| + // address 0 or the port 0). |
| + ADDRESS_INVALID = -108, |
| + |
| + // The IP address is unreachable. This usually means that there is no route to |
| + // the specified host or network. |
| + ADDRESS_UNREACHABLE = -109, |
| + |
| + // The server requested a client certificate for SSL client authentication. |
| + SSL_CLIENT_AUTH_CERT_NEEDED = -110, |
| + |
| + // A tunnel connection through the proxy could not be established. |
| + TUNNEL_CONNECTION_FAILED = -111, |
| + |
| + // No SSL protocol versions are enabled. |
| + NO_SSL_VERSIONS_ENABLED = -112, |
| + |
| + // The client and server don't support a common SSL protocol version or |
| + // cipher suite. |
| + SSL_VERSION_OR_CIPHER_MISMATCH = -113, |
| + |
| + // The server requested a renegotiation (rehandshake). |
| + SSL_RENEGOTIATION_REQUESTED = -114, |
| + |
| + // The proxy requested authentication (for tunnel establishment) with an |
| + // unsupported method. |
| + PROXY_AUTH_UNSUPPORTED = -115, |
| + |
| + // During SSL renegotiation (rehandshake), the server sent a certificate with |
| + // an error. |
| + // |
| + // Note: this error is not in the -2xx range so that it won't be handled as a |
| + // certificate error. |
| + CERT_ERROR_IN_SSL_RENEGOTIATION = -116, |
| + |
| + // The SSL handshake failed because of a bad or missing client certificate. |
| + BAD_SSL_CLIENT_AUTH_CERT = -117, |
| + |
| + // A connection attempt timed out. |
| + CONNECTION_TIMED_OUT = -118, |
| + |
| + // There are too many pending DNS resolves, so a request in the queue was |
| + // aborted. |
| + HOST_RESOLVER_QUEUE_TOO_LARGE = -119, |
| + |
| + // Failed establishing a connection to the SOCKS proxy server for a target |
| + // host. |
| + SOCKS_CONNECTION_FAILED = -120, |
| + |
| + // The SOCKS proxy server failed establishing connection to the target host |
| + // because that host is unreachable. |
| + SOCKS_CONNECTION_HOST_UNREACHABLE = -121, |
| + |
| + // The request to negotiate an alternate protocol failed. |
| + NPN_NEGOTIATION_FAILED = -122, |
| + |
| + // The peer sent an SSL no_renegotiation alert message. |
| + SSL_NO_RENEGOTIATION = -123, |
| + |
| + // Winsock sometimes reports more data written than passed. This is probably |
| + // due to a broken LSP. |
| + WINSOCK_UNEXPECTED_WRITTEN_BYTES = -124, |
| + |
| + // An SSL peer sent us a fatal decompression_failure alert. This typically |
| + // occurs when a peer selects DEFLATE compression in the mistaken belief that |
| + // it supports it. |
| + SSL_DECOMPRESSION_FAILURE_ALERT = -125, |
| + |
| + // An SSL peer sent us a fatal bad_record_mac alert. This has been observed |
| + // from servers with buggy DEFLATE support. |
| + SSL_BAD_RECORD_MAC_ALERT = -126, |
| + |
| + // The proxy requested authentication (for tunnel establishment). |
| + PROXY_AUTH_REQUESTED = -127, |
| + |
| + // A known TLS strict server didn't offer the renegotiation extension. |
| + SSL_UNSAFE_NEGOTIATION = -128, |
| + |
| + // The SSL server attempted to use a weak ephemeral Diffie-Hellman key. |
| + SSL_WEAK_SERVER_EPHEMERAL_DH_KEY = -129, |
| + |
| + // Could not create a connection to the proxy server. An error occurred |
| + // either in resolving its name, or in connecting a socket to it. |
| + // Note that this does NOT include failures during the actual "CONNECT" method |
| + // of an HTTP proxy. |
| + PROXY_CONNECTION_FAILED = -130, |
| + |
| + // A mandatory proxy configuration could not be used. Currently this means |
| + // that a mandatory PAC script could not be fetched, parsed or executed. |
| + MANDATORY_PROXY_CONFIGURATION_FAILED = -131, |
| + |
| + // We've hit the max socket limit for the socket pool while preconnecting. We |
| + // don't bother trying to preconnect more sockets. |
| + PRECONNECT_MAX_SOCKET_LIMIT = -133, |
| + |
| + // The permission to use the SSL client certificate's private key was denied. |
| + SSL_CLIENT_AUTH_PRIVATE_KEY_ACCESS_DENIED = -134, |
| + |
| + // The SSL client certificate has no private key. |
| + SSL_CLIENT_AUTH_CERT_NO_PRIVATE_KEY = -135, |
| + |
| + // The certificate presented by the HTTPS Proxy was invalid. |
| + PROXY_CERTIFICATE_INVALID = -136, |
| + |
| + // An error occurred when trying to do a name resolution (DNS). |
| + NAME_RESOLUTION_FAILED = -137, |
| + |
| + // 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. See also ERR_ACCESS_DENIED. |
| + NETWORK_ACCESS_DENIED = -138, |
| + |
| + // The request throttler module cancelled this request to avoid DDOS. |
| + TEMPORARILY_THROTTLED = -139, |
| + |
| + // A request to create an SSL tunnel connection through the HTTPS proxy |
| + // received a non-200 (OK) and non-407 (Proxy Auth) response. The response |
| + // body might include a description of why the request failed. |
| + HTTPS_PROXY_TUNNEL_RESPONSE = -140, |
| + |
| + // 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. |
| + SSL_CLIENT_AUTH_SIGNATURE_FAILED = -141, |
| + |
| + // The message was too large for the transport. (for example a UDP message |
| + // which exceeds size threshold). |
| + MSG_TOO_BIG = -142, |
| + |
| + // A SPDY session already exists, and should be used instead of this |
| + // connection. |
| + SPDY_SESSION_ALREADY_EXISTS = -143, |
| + |
| + // Websocket protocol error. Indicates that we are terminating the connection |
| + // due to a malformed frame or other protocol violation. |
| + WS_PROTOCOL_ERROR = -145, |
| + |
| + // Connection was aborted for switching to another ptotocol. |
| + // WebSocket abort SocketStream connection when alternate protocol is found. |
| + PROTOCOL_SWITCHED = -146, |
| + |
| + // Returned when attempting to bind an address that is already in use. |
| + ADDRESS_IN_USE = -147, |
| + |
| + // An operation failed because the SSL handshake has not completed. |
| + SSL_HANDSHAKE_NOT_COMPLETED = -148, |
| + |
| + // SSL peer's public key is invalid. |
| + SSL_BAD_PEER_PUBLIC_KEY = -149, |
| + |
| + // The certificate didn't match the built-in public key pins for the host |
| + // name. The pins are set in net/http/transport_security_state.cc and require |
| + // that one of a set of public keys exist on the path from the leaf to the |
| + // root. |
| + SSL_PINNED_KEY_NOT_IN_CERT_CHAIN = -150, |
| + |
| + // Server request for client certificate did not contain any types we support. |
| + CLIENT_AUTH_CERT_TYPE_UNSUPPORTED = -151, |
| + |
| + // Server requested one type of cert, then requested a different type while |
| + // the first was still being generated. |
| + ORIGIN_BOUND_CERT_GENERATION_TYPE_MISMATCH = -152, |
| + |
| + // An SSL peer sent us a fatal decrypt_error alert. This typically occurs when |
| + // a peer could not correctly verify a signature (in CertificateVerify or |
| + // ServerKeyExchange) or validate a Finished message. |
| + SSL_DECRYPT_ERROR_ALERT = -153, |
| + |
| + // There are too many pending WebSocketJob instances, so the new job was not |
| + // pushed to the queue. |
| + WS_THROTTLE_QUEUE_TOO_LARGE = -154, |
| + |
| + // There are too many active SocketStream instances, so the new connect |
| + // request was rejected. |
| + TOO_MANY_SOCKET_STREAMS = -155, |
| + |
| + // The SSL server certificate changed in a renegotiation. |
| + SSL_SERVER_CERT_CHANGED = -156, |
| + |
| + // The SSL server indicated that an unnecessary TLS version fallback was |
| + // performed. |
| + SSL_INAPPROPRIATE_FALLBACK = -157, |
| + |
| + // Certificate Transparency: All Signed Certificate Timestamps failed to |
| + // verify. |
| + CT_NO_SCTS_VERIFIED_OK = -158, |
| + |
| + // The SSL server sent us a fatal unrecognized_name alert. |
| + SSL_UNRECOGNIZED_NAME_ALERT = -159, |
| + |
| + // Failed to set the socket's receive buffer size as requested. |
| + SOCKET_SET_RECEIVE_BUFFER_SIZE_ERROR = -160, |
| + |
| + // Failed to set the socket's send buffer size as requested. |
| + SOCKET_SET_SEND_BUFFER_SIZE_ERROR = -161, |
| + |
| + // Failed to set the socket's receive buffer size as requested, despite |
| + // success return code from setsockopt. |
| + SOCKET_RECEIVE_BUFFER_SIZE_UNCHANGEABLE = -162, |
| + |
| + // Failed to set the socket's send buffer size as requested, despite success |
| + // return code from setsockopt. |
| + SOCKET_SEND_BUFFER_SIZE_UNCHANGEABLE = -163, |
| + |
| + // Failed to import a client certificate from the platform store into the SSL |
| + // library. |
| + SSL_CLIENT_AUTH_CERT_BAD_FORMAT = -164, |
| + |
| + // The SSL server requires falling back to a version older than the configured |
| + // minimum fallback version, and thus fallback failed. |
| + SSL_FALLBACK_BEYOND_MINIMUM_VERSION = -165 |
| +}; |