New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 659662 link

Starred by 11 users

Issue metadata

Status: Fixed
Last visit > 30 days ago
Closed: Mar 2017
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

issue 696350

Sign in to add a comment

Allow handling certificate errors via DevTools

Project Member Reported by, Oct 26 2016

Issue description

For headless, we can't show a UI warning for bad certificates as chrome does. Instead, we should investigate exposing certificate errors as events through DevTools and controlling what action to take through a DevTools command.

FYI, currently such errors are handled in SSLManager::OnCertErrorInternal, which delegates to ContentBrowserClient::AllowCertificateError.
Labels: HeadlessUpForGrabs
Labels: -HeadlessUpForGrabs
Status: Started (was: Available)

Comment 4 by, Feb 27 2017

Components: Internals>Network>Certificate UI>Browser>Interstitials
Adding Certificate and Interstitials owners, since this would give DevTools the ability to handle/bypass interstitials.
Blocking: 696350
 Issue 697721  has been merged into this issue.
Project Member

Comment 7 by, Mar 22 2017

The following revision refers to this bug:

commit 8452ddd64771d3573cd7083f3e6e263cf67fbe1b
Author: irisu <>
Date: Wed Mar 22 07:46:14 2017

Add certificate error handling to devtools.

This is necessary as headless chrome cannot show a UI warning for SSL
certificate errors. Instead, we can expose the errors as DevTools events
and control the action to take through a DevTools command.

BUG= 659662 

Cr-Commit-Position: refs/heads/master@{#458673}


Comment 8 by, Mar 23 2017

Status: Fixed (was: Started)
Labels: M-59

Sign in to add a comment