Allow to ignore certificate errors during navigation

There should be a capability to ignore certificate errors during navigation. See https://github.com/GoogleChrome/puppeteer/issues/66 for proposal and https://github.com/cyrus-and/chrome-remote-interface/issues/183 for original discussion.

For example, we can add ignoreSSL navigation option:

page.navigate('https://example.com', { ignoreSSL: true })

[Garbee]

I’d urge it be more tedious to ignore per navigation since you really shouldn’t be ignoring problems like that. Even in a test suite, it’s not something to encourage.

[aslushnikov]

More details on this. The certificates behave a little surprising - once a certain certificate error was “ignored” via protocol’s Security.handleCertificateError, the certificate would not trigger any errors in future.

This would result in inability to do Page.setIgnoreHTTPSErrors(false), which causes the test failure in the #176.

Upstream bug: https://bugs.chromium.org/p/chromium/issues/detail?id=751204. We spent half a day with @allada debugging the issue but it didn’t get us anywhere.

To move on with this, since there’s no practical need to do setIgnoreHTTPSErrors(false), we can have a browser option to ignore HTTPS errors:

const {Browser} = require('puppeteer');
const browser = new Browser({ignoreHTTPSErrors: true});
...