Chromium network errors for Chromium-based JavaScript environments
npm install chromium-net-errors-urlboxChromium Network Errors
=======================
Provides Chromium network errors found in
net_error_list.h
as custom errors for Node.js.
They correspond to the error codes that could be provided by
Electron's did-fail-load event, for
example.
``sh`
npm install chromium-net-errors --save
`js
var app = require('app');
var BrowserWindow = require('browser-window');
var networkErrors = require('chromium-net-errors');
app.on('ready', function () {
var win = new BrowserWindow({ width: 800, height: 600 });
win.webContents.on('did-fail-load', function (e, errorCode) {
throw networkErrors.createByCode(errorCode);
});
win.loadUrl('http://blablanotexist.com');
});
`
Will pop-up the following error:
`
Uncaught Exception:
NameNotResolvedError: The host name could not be resolved.
at Object.exports.createByCode (/tmp/ele/node_modules/chromium-net-errors/index.js:72:9)
at EventEmitter.
at emitThree (events.js:97:13)
at EventEmitter.emit (events.js:172:7)
`js`
var cne = require('chromium-net-errors');
`js
var err = new cne.ConnectionTimedOutError();
console.log(err instanceof Error); // true
console.log(err instanceof cne.ChromiumNetError); // true
console.log(err instanceof cne.ConnectionTimedOutError); // true
`
`js
var err = cne.createByCode(-201);
console.log(err instanceof cne.CertDateInvalidError);
// true
console.log(err.isCertificateError());
// true
console.log(err.type);
// certificate
console.log(err.message);
// 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 his public key and is signed by his 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).
``
MIT