Chromium network errors for Electron and Chromium-based JavaScript environments
npm install chromium-net-errorsChromium Network Errors
=======================
Provides Chromium network errors found in
net_error_list.h
as custom error classes that can be conveniently used in Node.js, Electron apps and browsers.
The errors correspond to the error codes that are provided in Electron'sdid-fail-load events of the WebContents class
and the webview tag.
Features |
Installation |
Electron Example |
Usage |
List of Errors |
License
- No dependencies.
- 100% test coverage.
- ES6 build with import and export, and a CommonJS build. Your bundler can
use the ES6 modules if it supports the "module" or "jsnext:main"
directives in the package.json.
- Daily cron-triggered checks for updates on net_error_list.h on
Travis CI
to always get the most up-to-date list of errors.
``sh`
npm install chromium-net-errors --save
`js`
import * as chromiumNetErrors from 'chromium-net-errors';
// or
const chromiumNetErrors = require('chromium-net-errors');
`js
import { app, BrowserWindow } from 'electron';
import * as chromiumNetErrors from 'chromium-net-errors';
app.on('ready', () => {
const win = new BrowserWindow({
width: 800,
height: 600,
});
win.webContents.on('did-fail-load', (event) => {
try {
const Err = chromiumNetErrors.getErrorByCode(event.errorCode);
throw new Err();
} catch (err) {
if (err instanceof chromiumNetErrors.NameNotResolvedError) {
console.error(The name '${event.validatedURL}' could not be resolved:\n ${err.message});Something went wrong while loading ${event.validatedURL}
} else {
console.error();
}
}
});
win.loadURL('http://blablanotexist.com');
});
`
`js`
import * as chromiumNetErrors from 'chromium-net-errors';
`js
const err = new chromiumNetErrors.ConnectionTimedOutError();
console.log(err instanceof Error);
// true
console.log(err instanceof chromiumNetErrors.ChromiumNetError);
// true
console.log(err instanceof chromiumNetErrors.ConnectionTimedOutError);
// true
`
`js
function thrower() {
throw new chromiumNetErrors.ConnectionTimedOutError();
}
try {
thrower();
} catch (err) {
console.log(err instanceof Error);
// true
console.log(err instanceof chromiumNetErrors.ChromiumNetError);
// true
console.log(err instanceof chromiumNetErrors.ConnectionTimedOutError);
// true
}
`
Get the class of an error by its errorCode.
`js
const Err = chromiumNetErrors.getErrorByCode(-201);
const err = new Err();
console.log(err instanceof chromiumNetErrors.CertDateInvalidError);
// true
console.log(err.isCertificateError());
// true
console.log(err.type);
// 'certificate'
console.log(err.message);
// The server responded with a certificate that, by our clock, appears to
// either not yet be valid or to have expired. This could mean:
//
// 1. An attacker is presenting an old certificate for which they have
// managed to obtain the private key.
//
// 2. The server is misconfigured and is not presenting a valid cert.
//
// 3. Our clock is wrong.
`
Get the class of an error by its errorDescription.
`js
const Err = chromiumNetErrors.getErrorByDescription('CERT_DATE_INVALID');
const err = new Err();
console.log(err instanceof chromiumNetErrors.CertDateInvalidError);
// true
console.log(err.isCertificateError());
// true
console.log(err.type);
// 'certificate'
console.log(err.message);
// The server responded with a certificate that, by our clock, appears to
// either not yet be valid or to have expired. This could mean:
//
// 1. An attacker is presenting an old certificate for which they have
// managed to obtain the private key.
//
// 2. The server is misconfigured and is not presenting a valid cert.
//
// 3. Our clock is wrong.
`
Get an array of all possible errors.
`js
console.log(chromiumNetErrors.getErrors());
// [ { name: 'IoPendingError',
// code: -1,
// description: 'IO_PENDING',
// type: 'system',
// message: 'An asynchronous IO operation is not yet complete. This usually does not\nindicate a fatal error. Typically this error will be generated as a\nnotification to wait for some external notification that the IO operation\nfinally completed.' },
// { name: 'FailedError',
// code: -2,
// description: 'FAILED',
// type: 'system',
// message: 'A generic failure occurred.' },
// { name: 'AbortedError',
// code: -3,
// description: 'ABORTED',
// type: 'system',
// message: 'An operation was aborted (due to user action).' },
// { name: 'InvalidArgumentError',
// code: -4,
// description: 'INVALID_ARGUMENT',
// type: 'system',
// message: 'An argument to the function is incorrect.' },
// { name: 'InvalidHandleError',
// code: -5,
// description: 'INVALID_HANDLE',
// type: 'system',
// message: 'The handle or file descriptor is invalid.' },
// ...
// ]
`
> 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.
- Name: IoPendingError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.IoPendingError();
// or
const Err = chromiumNetErrors.getErrorByCode(-1);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('IO_PENDING');
const err = new Err();
> A generic failure occurred.
- Name: FailedError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.FailedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-2);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('FAILED');
const err = new Err();
> An operation was aborted (due to user action).
- Name: AbortedError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.AbortedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-3);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('ABORTED');
const err = new Err();
> An argument to the function is incorrect.
- Name: InvalidArgumentError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.InvalidArgumentError();
// or
const Err = chromiumNetErrors.getErrorByCode(-4);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('INVALID_ARGUMENT');
const err = new Err();
> The handle or file descriptor is invalid.
- Name: InvalidHandleError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.InvalidHandleError();
// or
const Err = chromiumNetErrors.getErrorByCode(-5);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('INVALID_HANDLE');
const err = new Err();
> The file or directory cannot be found.
- Name: FileNotFoundError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.FileNotFoundError();
// or
const Err = chromiumNetErrors.getErrorByCode(-6);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('FILE_NOT_FOUND');
const err = new Err();
> An operation timed out.
- Name: TimedOutError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.TimedOutError();
// or
const Err = chromiumNetErrors.getErrorByCode(-7);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('TIMED_OUT');
const err = new Err();
> The file is too large.
- Name: FileTooBigError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.FileTooBigError();
// or
const Err = chromiumNetErrors.getErrorByCode(-8);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('FILE_TOO_BIG');
const err = new Err();
> An unexpected error. This may be caused by a programming mistake or an
> invalid assumption.
- Name: UnexpectedError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.UnexpectedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-9);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('UNEXPECTED');
const err = new Err();
> Permission to access a resource, other than the network, was denied.
- Name: AccessDeniedError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.AccessDeniedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-10);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('ACCESS_DENIED');
const err = new Err();
> The operation failed because of unimplemented functionality.
- Name: NotImplementedError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.NotImplementedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-11);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('NOT_IMPLEMENTED');
const err = new Err();
> There were not enough resources to complete the operation.
- Name: InsufficientResourcesError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.InsufficientResourcesError();
// or
const Err = chromiumNetErrors.getErrorByCode(-12);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('INSUFFICIENT_RESOURCES');
const err = new Err();
> Memory allocation failed.
- Name: OutOfMemoryError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.OutOfMemoryError();
// or
const Err = chromiumNetErrors.getErrorByCode(-13);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('OUT_OF_MEMORY');
const err = new Err();
> The file upload failed because the file's modification time was different
> from the expectation.
- Name: UploadFileChangedError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.UploadFileChangedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-14);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('UPLOAD_FILE_CHANGED');
const err = new Err();
> The socket is not connected.
- Name: SocketNotConnectedError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.SocketNotConnectedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-15);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('SOCKET_NOT_CONNECTED');
const err = new Err();
> The file already exists.
- Name: FileExistsError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.FileExistsError();
// or
const Err = chromiumNetErrors.getErrorByCode(-16);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('FILE_EXISTS');
const err = new Err();
> The path or file name is too long.
- Name: FilePathTooLongError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.FilePathTooLongError();
// or
const Err = chromiumNetErrors.getErrorByCode(-17);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('FILE_PATH_TOO_LONG');
const err = new Err();
> Not enough room left on the disk.
- Name: FileNoSpaceError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.FileNoSpaceError();
// or
const Err = chromiumNetErrors.getErrorByCode(-18);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('FILE_NO_SPACE');
const err = new Err();
> The file has a virus.
- Name: FileVirusInfectedError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.FileVirusInfectedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-19);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('FILE_VIRUS_INFECTED');
const err = new Err();
> The client chose to block the request.
- Name: BlockedByClientError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.BlockedByClientError();
// or
const Err = chromiumNetErrors.getErrorByCode(-20);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('BLOCKED_BY_CLIENT');
const err = new Err();
> The network changed.
- Name: NetworkChangedError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.NetworkChangedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-21);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('NETWORK_CHANGED');
const err = new Err();
> The request was blocked by the URL block list configured by the domain
> administrator.
- Name: BlockedByAdministratorError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.BlockedByAdministratorError();
// or
const Err = chromiumNetErrors.getErrorByCode(-22);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('BLOCKED_BY_ADMINISTRATOR');
const err = new Err();
> The socket is already connected.
- Name: SocketIsConnectedError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.SocketIsConnectedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-23);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('SOCKET_IS_CONNECTED');
const err = new Err();
> 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.
- Name: BlockedEnrollmentCheckPendingError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.BlockedEnrollmentCheckPendingError();
// or
const Err = chromiumNetErrors.getErrorByCode(-24);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('BLOCKED_ENROLLMENT_CHECK_PENDING');
const err = new Err();
> 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.
- Name: UploadStreamRewindNotSupportedError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.UploadStreamRewindNotSupportedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-25);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('UPLOAD_STREAM_REWIND_NOT_SUPPORTED');
const err = new Err();
> The request failed because the URLRequestContext is shutting down, or has
> been shut down.
- Name: ContextShutDownError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.ContextShutDownError();
// or
const Err = chromiumNetErrors.getErrorByCode(-26);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('CONTEXT_SHUT_DOWN');
const err = new Err();
> The request failed because the response was delivered along with requirements
> which are not met ('X-Frame-Options' and 'Content-Security-Policy' ancestor
> checks and 'Cross-Origin-Resource-Policy', for instance).
- Name: BlockedByResponseError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.BlockedByResponseError();
// or
const Err = chromiumNetErrors.getErrorByCode(-27);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('BLOCKED_BY_RESPONSE');
const err = new Err();
> The request was blocked by system policy disallowing some or all cleartext
> requests. Used for NetworkSecurityPolicy on Android.
- Name: CleartextNotPermittedError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.CleartextNotPermittedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-29);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('CLEARTEXT_NOT_PERMITTED');
const err = new Err();
> The request was blocked by a Content Security Policy
- Name: BlockedByCspError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.BlockedByCspError();
// or
const Err = chromiumNetErrors.getErrorByCode(-30);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('BLOCKED_BY_CSP');
const err = new Err();
> The request was blocked because of no H/2 or QUIC session.
- Name: H2OrQuicRequiredError
- Code:
- Description:
- Type: system
`js`
const err = new chromiumNetErrors.H2OrQuicRequiredError();
// or
const Err = chromiumNetErrors.getErrorByCode(-31);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('H2_OR_QUIC_REQUIRED');
const err = new Err();
> A connection was closed (corresponding to a TCP FIN).
- Name: ConnectionClosedError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.ConnectionClosedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-100);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('CONNECTION_CLOSED');
const err = new Err();
> A connection was reset (corresponding to a TCP RST).
- Name: ConnectionResetError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.ConnectionResetError();
// or
const Err = chromiumNetErrors.getErrorByCode(-101);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('CONNECTION_RESET');
const err = new Err();
> A connection attempt was refused.
- Name: ConnectionRefusedError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.ConnectionRefusedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-102);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('CONNECTION_REFUSED');
const err = new Err();
> 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.
- Name: ConnectionAbortedError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.ConnectionAbortedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-103);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('CONNECTION_ABORTED');
const err = new Err();
> A connection attempt failed.
- Name: ConnectionFailedError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.ConnectionFailedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-104);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('CONNECTION_FAILED');
const err = new Err();
> The host name could not be resolved.
- Name: NameNotResolvedError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.NameNotResolvedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-105);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('NAME_NOT_RESOLVED');
const err = new Err();
> The Internet connection has been lost.
- Name: InternetDisconnectedError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.InternetDisconnectedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-106);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('INTERNET_DISCONNECTED');
const err = new Err();
> An SSL protocol error occurred.
- Name: SslProtocolError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.SslProtocolError();
// or
const Err = chromiumNetErrors.getErrorByCode(-107);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('SSL_PROTOCOL_ERROR');
const err = new Err();
> The IP address or port number is invalid (e.g., cannot connect to the IP
> address 0 or the port 0).
- Name: AddressInvalidError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.AddressInvalidError();
// or
const Err = chromiumNetErrors.getErrorByCode(-108);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('ADDRESS_INVALID');
const err = new Err();
> The IP address is unreachable. This usually means that there is no route to
> the specified host or network.
- Name: AddressUnreachableError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.AddressUnreachableError();
// or
const Err = chromiumNetErrors.getErrorByCode(-109);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('ADDRESS_UNREACHABLE');
const err = new Err();
> The server requested a client certificate for SSL client authentication.
- Name: SslClientAuthCertNeededError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.SslClientAuthCertNeededError();
// or
const Err = chromiumNetErrors.getErrorByCode(-110);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('SSL_CLIENT_AUTH_CERT_NEEDED');
const err = new Err();
> A tunnel connection through the proxy could not be established.
- Name: TunnelConnectionFailedError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.TunnelConnectionFailedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-111);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('TUNNEL_CONNECTION_FAILED');
const err = new Err();
> No SSL protocol versions are enabled.
- Name: NoSslVersionsEnabledError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.NoSslVersionsEnabledError();
// or
const Err = chromiumNetErrors.getErrorByCode(-112);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('NO_SSL_VERSIONS_ENABLED');
const err = new Err();
> The client and server don't support a common SSL protocol version or
> cipher suite.
- Name: SslVersionOrCipherMismatchError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.SslVersionOrCipherMismatchError();
// or
const Err = chromiumNetErrors.getErrorByCode(-113);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('SSL_VERSION_OR_CIPHER_MISMATCH');
const err = new Err();
> The server requested a renegotiation (rehandshake).
- Name: SslRenegotiationRequestedError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.SslRenegotiationRequestedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-114);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('SSL_RENEGOTIATION_REQUESTED');
const err = new Err();
> The proxy requested authentication (for tunnel establishment) with an
> unsupported method.
- Name: ProxyAuthUnsupportedError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.ProxyAuthUnsupportedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-115);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('PROXY_AUTH_UNSUPPORTED');
const err = new Err();
> 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.
- Name: CertErrorInSslRenegotiationError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.CertErrorInSslRenegotiationError();
// or
const Err = chromiumNetErrors.getErrorByCode(-116);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('CERT_ERROR_IN_SSL_RENEGOTIATION');
const err = new Err();
> The SSL handshake failed because of a bad or missing client certificate.
- Name: BadSslClientAuthCertError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.BadSslClientAuthCertError();
// or
const Err = chromiumNetErrors.getErrorByCode(-117);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('BAD_SSL_CLIENT_AUTH_CERT');
const err = new Err();
> A connection attempt timed out.
- Name: ConnectionTimedOutError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.ConnectionTimedOutError();
// or
const Err = chromiumNetErrors.getErrorByCode(-118);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('CONNECTION_TIMED_OUT');
const err = new Err();
> There are too many pending DNS resolves, so a request in the queue was
> aborted.
- Name: HostResolverQueueTooLargeError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.HostResolverQueueTooLargeError();
// or
const Err = chromiumNetErrors.getErrorByCode(-119);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('HOST_RESOLVER_QUEUE_TOO_LARGE');
const err = new Err();
> Failed establishing a connection to the SOCKS proxy server for a target host.
- Name: SocksConnectionFailedError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.SocksConnectionFailedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-120);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('SOCKS_CONNECTION_FAILED');
const err = new Err();
> The SOCKS proxy server failed establishing connection to the target host
> because that host is unreachable.
- Name: SocksConnectionHostUnreachableError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.SocksConnectionHostUnreachableError();
// or
const Err = chromiumNetErrors.getErrorByCode(-121);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('SOCKS_CONNECTION_HOST_UNREACHABLE');
const err = new Err();
> The request to negotiate an alternate protocol failed.
- Name: AlpnNegotiationFailedError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.AlpnNegotiationFailedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-122);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('ALPN_NEGOTIATION_FAILED');
const err = new Err();
> The peer sent an SSL no_renegotiation alert message.
- Name: SslNoRenegotiationError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.SslNoRenegotiationError();
// or
const Err = chromiumNetErrors.getErrorByCode(-123);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('SSL_NO_RENEGOTIATION');
const err = new Err();
> Winsock sometimes reports more data written than passed. This is probably
> due to a broken LSP.
- Name: WinsockUnexpectedWrittenBytesError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.WinsockUnexpectedWrittenBytesError();
// or
const Err = chromiumNetErrors.getErrorByCode(-124);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('WINSOCK_UNEXPECTED_WRITTEN_BYTES');
const err = new Err();
> 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.
- Name: SslDecompressionFailureAlertError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.SslDecompressionFailureAlertError();
// or
const Err = chromiumNetErrors.getErrorByCode(-125);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('SSL_DECOMPRESSION_FAILURE_ALERT');
const err = new Err();
> An SSL peer sent us a fatal bad_record_mac alert. This has been observed
> from servers with buggy DEFLATE support.
- Name: SslBadRecordMacAlertError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.SslBadRecordMacAlertError();
// or
const Err = chromiumNetErrors.getErrorByCode(-126);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('SSL_BAD_RECORD_MAC_ALERT');
const err = new Err();
> The proxy requested authentication (for tunnel establishment).
- Name: ProxyAuthRequestedError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.ProxyAuthRequestedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-127);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('PROXY_AUTH_REQUESTED');
const err = new Err();
> 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.
- Name: ProxyConnectionFailedError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.ProxyConnectionFailedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-130);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('PROXY_CONNECTION_FAILED');
const err = new Err();
> A mandatory proxy configuration could not be used. Currently this means
> that a mandatory PAC script could not be fetched, parsed or executed.
- Name: MandatoryProxyConfigurationFailedError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.MandatoryProxyConfigurationFailedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-131);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('MANDATORY_PROXY_CONFIGURATION_FAILED');
const err = new Err();
> We've hit the max socket limit for the socket pool while preconnecting. We
> don't bother trying to preconnect more sockets.
- Name: PreconnectMaxSocketLimitError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.PreconnectMaxSocketLimitError();
// or
const Err = chromiumNetErrors.getErrorByCode(-133);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('PRECONNECT_MAX_SOCKET_LIMIT');
const err = new Err();
> The permission to use the SSL client certificate's private key was denied.
- Name: SslClientAuthPrivateKeyAccessDeniedError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.SslClientAuthPrivateKeyAccessDeniedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-134);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('SSL_CLIENT_AUTH_PRIVATE_KEY_ACCESS_DENIED');
const err = new Err();
> The SSL client certificate has no private key.
- Name: SslClientAuthCertNoPrivateKeyError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.SslClientAuthCertNoPrivateKeyError();
// or
const Err = chromiumNetErrors.getErrorByCode(-135);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('SSL_CLIENT_AUTH_CERT_NO_PRIVATE_KEY');
const err = new Err();
> The certificate presented by the HTTPS Proxy was invalid.
- Name: ProxyCertificateInvalidError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.ProxyCertificateInvalidError();
// or
const Err = chromiumNetErrors.getErrorByCode(-136);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('PROXY_CERTIFICATE_INVALID');
const err = new Err();
> An error occurred when trying to do a name resolution (DNS).
- Name: NameResolutionFailedError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.NameResolutionFailedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-137);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('NAME_RESOLUTION_FAILED');
const err = new Err();
> 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.
- Name: NetworkAccessDeniedError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.NetworkAccessDeniedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-138);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('NETWORK_ACCESS_DENIED');
const err = new Err();
> The request throttler module cancelled this request to avoid DDOS.
- Name: TemporarilyThrottledError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.TemporarilyThrottledError();
// or
const Err = chromiumNetErrors.getErrorByCode(-139);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('TEMPORARILY_THROTTLED');
const err = new Err();
> A request to create an SSL tunnel connection through the HTTPS proxy
> received a 302 (temporary redirect) response. The response body might
> include a description of why the request failed.
>
> TODO(https://crbug.com/928551): This is deprecated and should not be used by
> new code.
- Name: HttpsProxyTunnelResponseRedirectError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.HttpsProxyTunnelResponseRedirectError();
// or
const Err = chromiumNetErrors.getErrorByCode(-140);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('HTTPS_PROXY_TUNNEL_RESPONSE_REDIRECT');
const err = new Err();
> 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.
- Name: SslClientAuthSignatureFailedError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.SslClientAuthSignatureFailedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-141);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('SSL_CLIENT_AUTH_SIGNATURE_FAILED');
const err = new Err();
> The message was too large for the transport. (for example a UDP message
> which exceeds size threshold).
- Name: MsgTooBigError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.MsgTooBigError();
// or
const Err = chromiumNetErrors.getErrorByCode(-142);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('MSG_TOO_BIG');
const err = new Err();
> Websocket protocol error. Indicates that we are terminating the connection
> due to a malformed frame or other protocol violation.
- Name: WsProtocolError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.WsProtocolError();
// or
const Err = chromiumNetErrors.getErrorByCode(-145);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('WS_PROTOCOL_ERROR');
const err = new Err();
> Returned when attempting to bind an address that is already in use.
- Name: AddressInUseError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.AddressInUseError();
// or
const Err = chromiumNetErrors.getErrorByCode(-147);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('ADDRESS_IN_USE');
const err = new Err();
> An operation failed because the SSL handshake has not completed.
- Name: SslHandshakeNotCompletedError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.SslHandshakeNotCompletedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-148);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('SSL_HANDSHAKE_NOT_COMPLETED');
const err = new Err();
> SSL peer's public key is invalid.
- Name: SslBadPeerPublicKeyError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.SslBadPeerPublicKeyError();
// or
const Err = chromiumNetErrors.getErrorByCode(-149);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('SSL_BAD_PEER_PUBLIC_KEY');
const err = new Err();
> 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.
- Name: SslPinnedKeyNotInCertChainError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.SslPinnedKeyNotInCertChainError();
// or
const Err = chromiumNetErrors.getErrorByCode(-150);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('SSL_PINNED_KEY_NOT_IN_CERT_CHAIN');
const err = new Err();
> Server request for client certificate did not contain any types we support.
- Name: ClientAuthCertTypeUnsupportedError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.ClientAuthCertTypeUnsupportedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-151);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('CLIENT_AUTH_CERT_TYPE_UNSUPPORTED');
const err = new Err();
> 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.
- Name: SslDecryptErrorAlertError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.SslDecryptErrorAlertError();
// or
const Err = chromiumNetErrors.getErrorByCode(-153);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('SSL_DECRYPT_ERROR_ALERT');
const err = new Err();
> There are too many pending WebSocketJob instances, so the new job was not
> pushed to the queue.
- Name: WsThrottleQueueTooLargeError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.WsThrottleQueueTooLargeError();
// or
const Err = chromiumNetErrors.getErrorByCode(-154);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('WS_THROTTLE_QUEUE_TOO_LARGE');
const err = new Err();
> The SSL server certificate changed in a renegotiation.
- Name: SslServerCertChangedError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.SslServerCertChangedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-156);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('SSL_SERVER_CERT_CHANGED');
const err = new Err();
> The SSL server sent us a fatal unrecognized_name alert.
- Name: SslUnrecognizedNameAlertError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.SslUnrecognizedNameAlertError();
// or
const Err = chromiumNetErrors.getErrorByCode(-159);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('SSL_UNRECOGNIZED_NAME_ALERT');
const err = new Err();
> Failed to set the socket's receive buffer size as requested.
- Name: SocketSetReceiveBufferSizeError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.SocketSetReceiveBufferSizeError();
// or
const Err = chromiumNetErrors.getErrorByCode(-160);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('SOCKET_SET_RECEIVE_BUFFER_SIZE_ERROR');
const err = new Err();
> Failed to set the socket's send buffer size as requested.
- Name: SocketSetSendBufferSizeError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.SocketSetSendBufferSizeError();
// or
const Err = chromiumNetErrors.getErrorByCode(-161);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('SOCKET_SET_SEND_BUFFER_SIZE_ERROR');
const err = new Err();
> Failed to set the socket's receive buffer size as requested, despite success
> return code from setsockopt.
- Name: SocketReceiveBufferSizeUnchangeableError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.SocketReceiveBufferSizeUnchangeableError();
// or
const Err = chromiumNetErrors.getErrorByCode(-162);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('SOCKET_RECEIVE_BUFFER_SIZE_UNCHANGEABLE');
const err = new Err();
> Failed to set the socket's send buffer size as requested, despite success
> return code from setsockopt.
- Name: SocketSendBufferSizeUnchangeableError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.SocketSendBufferSizeUnchangeableError();
// or
const Err = chromiumNetErrors.getErrorByCode(-163);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('SOCKET_SEND_BUFFER_SIZE_UNCHANGEABLE');
const err = new Err();
> Failed to import a client certificate from the platform store into the SSL
> library.
- Name: SslClientAuthCertBadFormatError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.SslClientAuthCertBadFormatError();
// or
const Err = chromiumNetErrors.getErrorByCode(-164);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('SSL_CLIENT_AUTH_CERT_BAD_FORMAT');
const err = new Err();
> Resolving a hostname to an IP address list included the IPv4 address
> "127.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.
- Name: IcannNameCollisionError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.IcannNameCollisionError();
// or
const Err = chromiumNetErrors.getErrorByCode(-166);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('ICANN_NAME_COLLISION');
const err = new Err();
> The SSL server presented a certificate which could not be decoded. This is
> not a certificate error code as no X509Certificate object is available. This
> error is fatal.
- Name: SslServerCertBadFormatError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.SslServerCertBadFormatError();
// or
const Err = chromiumNetErrors.getErrorByCode(-167);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('SSL_SERVER_CERT_BAD_FORMAT');
const err = new Err();
> Certificate Transparency: Received a signed tree head that failed to parse.
- Name: CtSthParsingFailedError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.CtSthParsingFailedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-168);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('CT_STH_PARSING_FAILED');
const err = new Err();
> Certificate Transparency: Received a signed tree head whose JSON parsing was
> OK but was missing some of the fields.
- Name: CtSthIncompleteError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.CtSthIncompleteError();
// or
const Err = chromiumNetErrors.getErrorByCode(-169);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('CT_STH_INCOMPLETE');
const err = new Err();
> The attempt to reuse a connection to send proxy auth credentials failed
> before the AuthController was used to generate credentials. The caller should
> reuse the controller with a new connection. This error is only used
> internally by the network stack.
- Name: UnableToReuseConnectionForProxyAuthError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.UnableToReuseConnectionForProxyAuthError();
// or
const Err = chromiumNetErrors.getErrorByCode(-170);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('UNABLE_TO_REUSE_CONNECTION_FOR_PROXY_AUTH');
const err = new Err();
> Certificate Transparency: Failed to parse the received consistency proof.
- Name: CtConsistencyProofParsingFailedError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.CtConsistencyProofParsingFailedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-171);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('CT_CONSISTENCY_PROOF_PARSING_FAILED');
const err = new Err();
> 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.
- Name: SslObsoleteCipherError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.SslObsoleteCipherError();
// or
const Err = chromiumNetErrors.getErrorByCode(-172);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('SSL_OBSOLETE_CIPHER');
const err = new Err();
> When a WebSocket handshake is done successfully and the connection has been
> upgraded, the URLRequest is cancelled with this error code.
- Name: WsUpgradeError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.WsUpgradeError();
// or
const Err = chromiumNetErrors.getErrorByCode(-173);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('WS_UPGRADE');
const err = new Err();
> Socket ReadIfReady support is not implemented. This error should not be user
> visible, because the normal Read() method is used as a fallback.
- Name: ReadIfReadyNotImplementedError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.ReadIfReadyNotImplementedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-174);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('READ_IF_READY_NOT_IMPLEMENTED');
const err = new Err();
> No socket buffer space is available.
- Name: NoBufferSpaceError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.NoBufferSpaceError();
// or
const Err = chromiumNetErrors.getErrorByCode(-176);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('NO_BUFFER_SPACE');
const err = new Err();
> There were no common signature algorithms between our client certificate
> private key and the server's preferences.
- Name: SslClientAuthNoCommonAlgorithmsError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.SslClientAuthNoCommonAlgorithmsError();
// or
const Err = chromiumNetErrors.getErrorByCode(-177);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('SSL_CLIENT_AUTH_NO_COMMON_ALGORITHMS');
const err = new Err();
> 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.
- Name: EarlyDataRejectedError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.EarlyDataRejectedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-178);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('EARLY_DATA_REJECTED');
const err = new Err();
> 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 https://tools.ietf.org/html/rfc8446#appendix-D.3 for details.
- Name: WrongVersionOnEarlyDataError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.WrongVersionOnEarlyDataError();
// or
const Err = chromiumNetErrors.getErrorByCode(-179);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('WRONG_VERSION_ON_EARLY_DATA');
const err = new Err();
> 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. (See
> https://crbug.com/boringssl/226.)
- Name: Tls13DowngradeDetectedError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.Tls13DowngradeDetectedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-180);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('TLS13_DOWNGRADE_DETECTED');
const err = new Err();
> The server's certificate has a keyUsage extension incompatible with the
> negotiated TLS key exchange method.
- Name: SslKeyUsageIncompatibleError
- Code:
- Description:
- Type: connection
`js`
const err = new chromiumNetErrors.SslKeyUsageIncompatibleError();
// or
const Err = chromiumNetErrors.getErrorByCode(-181);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('SSL_KEY_USAGE_INCOMPATIBLE');
const err = new Err();
> The server responded with a certificate whose common name did not match
> the host name. This could mean:
>
> 1. An attacker has redirected our traffic to their server and is
> presenting a certificate for which they know the private key.
>
> 2. The server is misconfigured and responding with the wrong cert.
>
> 3. The user is on a wireless network and is being redirected to the
> network's login page.
>
> 4. The OS has used a DNS search suffix and the server doesn't have
> a certificate for the abbreviated name in the address bar.
>
- Name: CertCommonNameInvalidError
- Code:
- Description:
- Type: certificate
`js`
const err = new chromiumNetErrors.CertCommonNameInvalidError();
// or
const Err = chromiumNetErrors.getErrorByCode(-200);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('CERT_COMMON_NAME_INVALID');
const err = new Err();
> The server responded with a certificate that, by our clock, appears to
> either not yet be valid or to have expired. This could mean:
>
> 1. An attacker is presenting an old certificate for which they have
> managed to obtain the private key.
>
> 2. The server is misconfigured and is not presenting a valid cert.
>
> 3. Our clock is wrong.
>
- Name: CertDateInvalidError
- Code:
- Description:
- Type: certificate
`js`
const err = new chromiumNetErrors.CertDateInvalidError();
// or
const Err = chromiumNetErrors.getErrorByCode(-201);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('CERT_DATE_INVALID');
const err = new Err();
> The server responded with a certificate that is signed by an authority
> we don't trust. The could mean:
>
> 1. An attacker has substituted the real certificate for a cert that
> contains their public key and is signed by their cousin.
>
> 2. The server operator has a legitimate certificate from a CA we don't
> know about, but should trust.
>
> 3. The server is presenting a self-signed certificate, providing no
> defense against active attackers (but foiling passive attackers).
>
- Name: CertAuthorityInvalidError
- Code:
- Description:
- Type: certificate
`js`
const err = new chromiumNetErrors.CertAuthorityInvalidError();
// or
const Err = chromiumNetErrors.getErrorByCode(-202);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('CERT_AUTHORITY_INVALID');
const err = new Err();
> 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.
>
- Name: CertContainsErrorsError
- Code:
- Description:
- Type: certificate
`js`
const err = new chromiumNetErrors.CertContainsErrorsError();
// or
const Err = chromiumNetErrors.getErrorByCode(-203);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('CERT_CONTAINS_ERRORS');
const err = new Err();
> The certificate has no mechanism for determining if it is revoked. In
> effect, this certificate cannot be revoked.
- Name: CertNoRevocationMechanismError
- Code:
- Description:
- Type: certificate
`js`
const err = new chromiumNetErrors.CertNoRevocationMechanismError();
// or
const Err = chromiumNetErrors.getErrorByCode(-204);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('CERT_NO_REVOCATION_MECHANISM');
const err = new Err();
> Revocation information for the security certificate for this site is not
> available. This could mean:
>
> 1. An attacker has compromised the private key in the certificate and is
> blocking our attempt to find out that the cert was revoked.
>
> 2. The certificate is unrevoked, but the revocation server is busy or
> unavailable.
>
- Name: CertUnableToCheckRevocationError
- Code:
- Description:
- Type: certificate
`js`
const err = new chromiumNetErrors.CertUnableToCheckRevocationError();
// or
const Err = chromiumNetErrors.getErrorByCode(-205);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('CERT_UNABLE_TO_CHECK_REVOCATION');
const err = new Err();
> 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.
- Name: CertRevokedError
- Code:
- Description:
- Type: certificate
`js`
const err = new chromiumNetErrors.CertRevokedError();
// or
const Err = chromiumNetErrors.getErrorByCode(-206);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('CERT_REVOKED');
const err = new Err();
> 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."
>
- Name: CertInvalidError
- Code:
- Description:
- Type: certificate
`js`
const err = new chromiumNetErrors.CertInvalidError();
// or
const Err = chromiumNetErrors.getErrorByCode(-207);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('CERT_INVALID');
const err = new Err();
> The server responded with a certificate that is signed using a weak
> signature algorithm.
- Name: CertWeakSignatureAlgorithmError
- Code:
- Description:
- Type: certificate
`js`
const err = new chromiumNetErrors.CertWeakSignatureAlgorithmError();
// or
const Err = chromiumNetErrors.getErrorByCode(-208);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('CERT_WEAK_SIGNATURE_ALGORITHM');
const err = new Err();
> The host name specified in the certificate is not unique.
- Name: CertNonUniqueNameError
- Code:
- Description:
- Type: certificate
`js`
const err = new chromiumNetErrors.CertNonUniqueNameError();
// or
const Err = chromiumNetErrors.getErrorByCode(-210);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('CERT_NON_UNIQUE_NAME');
const err = new Err();
> The server responded with a certificate that contains a weak key (e.g.
> a too-small RSA key).
- Name: CertWeakKeyError
- Code:
- Description:
- Type: certificate
`js`
const err = new chromiumNetErrors.CertWeakKeyError();
// or
const Err = chromiumNetErrors.getErrorByCode(-211);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('CERT_WEAK_KEY');
const err = new Err();
> The certificate claimed DNS names that are in violation of name constraints.
- Name: CertNameConstraintViolationError
- Code:
- Description:
- Type: certificate
`js`
const err = new chromiumNetErrors.CertNameConstraintViolationError();
// or
const Err = chromiumNetErrors.getErrorByCode(-212);
const err = new Err();
// or
const Err = chromiumNetErrors.getErrorByDescription('CERT_NAME_CONSTRAINT_VIOLATION');
const err = new Err();
> The certificate's validity period is too long.
- Name: CertValidityTooLongError
- Code: