[CB-3576] Privately signed https links don't work in InAppBrowser

[montylee]

Privately signed https links don't work in InAppBrowser and are blocked
by default on the InAppBrowser. A new option 'validatessl' has been
added that can be specified while
launching the InAppBrowser:

window.open(url, '_blank', 'location=yes,validatessl=no');

Default value of 'validatessl' is 'yes'. This will allow users to ignore
SSL certificate errors caused while opening self-signed https URLs

[montylee]

Android pull request link: apache/cordova-android#63

[montylee]

Any update on this pull request?

[arjuntraj]

@montylee this s not wrkng 4 me

[chrispadfield]

Any update? This affects us as well; on enterprise intranets largely.

[shazron]

Thanks @montylee (sorry for this taking so long). The InAppBrowser repo has moved to github.com/apache/cordova-plugin-inappbrowser so please close this PR and submit the patch there.

[montylee]

Hi @shazron , i am not sure if this patch should go in now, specially after reading @marcel Kinard's comments on this link: https://issues.apache.org/jira/browse/CB-3576

I think someone from PhoneGap's team would work on user confirmation while trying to open self-signed URLs.

[shazron]

Thanks @montylee - the issue shall live on in that JIRA item. If you can close this PR that would be great.