Add certificate error handling to devtools.

third_party/WebKit/Source/core/inspector/browser_protocol.json

Index: third_party/WebKit/Source/core/inspector/browser_protocol.json
diff --git a/third_party/WebKit/Source/core/inspector/browser_protocol.json b/third_party/WebKit/Source/core/inspector/browser_protocol.json
index 731b2dcb5f7822fd866edea7c86642f3390e56d0..d75ed80d39c0dccb1a6d8ff8efe265cca0310f4f 100644
--- a/third_party/WebKit/Source/core/inspector/browser_protocol.json
+++ b/third_party/WebKit/Source/core/inspector/browser_protocol.json
@@ -896,6 +896,12 @@
                     { "name": "displayedInsecureContentStyle", "$ref": "SecurityState", "description": "Security state representing a page that displayed insecure content." }
                 ],
                 "description": "Information about insecure content on the page."
+            },
+            {
+                "id": "CertificateErrorAction",
+                "type": "string",
+                "enum": ["continue", "cancel", "deny"],
+                "description": "The action to take when a certificate error occurs. continue will continue processing the request, cancel will cancel the request using net::ERR_ANORTED and deny will deny the request using net::ERR_INSECURE_RESPONSE."

[Sami, 2017/02/08 14:58:43]

typo: ERR_ABORTED

[pfeldman, 2017/02/08 18:24:00]

For better or worse, we don't use internal terms when describing what protocol
command does.

[irisu, 2017/02/14 05:46:14]

Removed.

             }
         ],
         "commands": [
@@ -910,6 +916,18 @@
             {
                 "name": "showCertificateViewer",
                 "description": "Displays native dialog with the certificate details."
+            },
+            {
+                "name": "handleCertificateError",
+                "description": "Handles a certificate error.",
+                "parameters": [
+                    { "name": "eventID", "type": "integer", "description": "The ID of the event."},
+                    { "name": "action", "$ref": "CertificateErrorAction", "description": "The action to take on the certificate error." }
+                ]
+            },
+            {
+                "name": "enableCertificateErrorHandling",
+                "description": "Enables tracking certificate errors."
             }
         ],
         "events": [
@@ -923,6 +941,13 @@
                     { "name": "insecureContentStatus", "$ref": "InsecureContentStatus", "description": "Information about insecure content on the page." },
                     { "name": "summary", "type": "string", "description": "Overrides user-visible description of the state.", "optional": true }
                 ]
+            },
+            {
+                "name": "certificateError",
+                "description": "There is a certificate error.",
+                "parameters": [
+                    { "name": "eventID", "type": "integer", "description": "The ID of the event."}

[pfeldman, 2017/02/08 18:24:00]

It is unlikely that I can make a decision programmatically just based on the
event id, please provide error details. Or did you just want auto-responder
here? That might be easier to implement altogether.

[Eric Seckler, 2017/02/08 18:53:10]

Let's add some more information from the SSLManager to the event. I think this
part is still WIP :)

I'm not familiar with "auto-responder", but I think we'd like to let headless
embedders make decisions.

[irisu, 2017/02/14 05:46:14]

Added extra parameters. Any more parameters you'd like added?

[Eric Seckler, 2017/02/14 18:42:24]

I'd be great to include some info about the certificate, but I'd be happy to add
that later, too. WDYT, Pavel?

[irisu, 2017/02/16 00:24:30]

SSLInfo has a lot of fields we could add, but I'm not sure which would be the
most useful here. I think we could leave that for later.

+                ]
             }
         ]
     },