You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cordova.apache.org by "jcesarmobile (Jira)" <ji...@apache.org> on 2022/10/13 22:12:00 UTC

[jira] [Closed] (CB-5758) Give same behavior to InAppBrowser as CordovaWebView for self-signed certs

     [ https://issues.apache.org/jira/browse/CB-5758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jcesarmobile closed CB-5758.
----------------------------
    Resolution: Won't Do

closing as won't do as we shouldn't ignore certificate errors, in cordova is done only for development and it has not been removed because it would be breaking

> Give same behavior to InAppBrowser as CordovaWebView for self-signed certs
> --------------------------------------------------------------------------
>
>                 Key: CB-5758
>                 URL: https://issues.apache.org/jira/browse/CB-5758
>             Project: Apache Cordova
>          Issue Type: New Feature
>          Components: cordova-plugin-inappbrowser
>            Reporter: Marcel Kinard
>            Priority: Minor
>
> See CB-3576 for history. This is a request that came from there.
> At least on the Android platform, the main webview (CordovaWebView) will silently accept self-signed certs when debuggable="true" in AndroidManifest.xml. (Hopefully other platforms have a similar behavior in pre-production.) The goal of this new feature is to get InAppBrowser to have the same behavior as the main webview in this respect, which is does not have today. Then both the main webview and InAppBrowser will behave consistently when they encounter https connections that have a self-signed cert.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org