Implement Security.setIgnoreCertificateErrors
Categories
(Remote Protocol :: CDP, enhancement, P1)
Tracking
(firefox72 fixed)
Tracking | Status | |
---|---|---|
firefox72 | --- | fixed |
People
(Reporter: ato, Assigned: ato)
References
()
Details
(Whiteboard: [puppeteer-alpha])
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
Allows insecure TLS certificates to be bypassed.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
This implements an all-or-nothing insecure sweeping override that
bypasses security exceptions when loading documents with invalid
or otherwise bad TLS certificates.
Assignee | ||
Updated•5 years ago
|
Comment 2•5 years ago
|
||
This method is marked as deprecated in the CDP documentation, and also not listed as being used by Gutenberg (https://wiki.mozilla.org/Remote/GutenbergCDPUsage). Why does this block the alpha release?
Assignee | ||
Comment 3•5 years ago
|
||
(In reply to Henrik Skupin (:whimboo) [⌚️UTC+2] from comment #2)
This method is marked as deprecated in the CDP documentation,
and also not listed as being used by Gutenberg
(https://wiki.mozilla.org/Remote/GutenbergCDPUsage). Why does this
block the alpha release?
See https://phabricator.services.mozilla.com/D50838#1562109.
This was filed under the wrong name by me.
Assignee | ||
Updated•5 years ago
|
Updated•5 years ago
|
Comment 5•5 years ago
|
||
bugherder |
Comment 6•5 years ago
|
||
(In reply to Andreas Tolfsen 「:ato」 from comment #3)
See https://phabricator.services.mozilla.com/D50838#1562109.
This was filed under the wrong name by me.
To be fair I cannot find any instance under the Gutenberg repository which sets the ignoreHTTPSErrors
argument of the Puppeteer launcher to true
. Which means also this method is never called when running Gutenberg tests.
As such given by our definition of the alpha release it shouldn't be a blocker which we track in the dashboard. Or why do you think otherwise?
Comment 7•5 years ago
|
||
I chatted with David about it and the puppeteer-alpha definition is a bit flurry. Basically we should work on real blocking issues but given that we are in the collecting phase we would like see nearly each and every bug to be covered in the dashboard.
Updated•5 years ago
|
Updated•5 years ago
|
Updated•4 years ago
|
Description
•