[TIMOB-11227] Android: Add method to ignore invalid SSL certificate
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | High |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2012-10-05T19:47:01.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 3.0.0, Sprint 2012-20 Core, 2012 Sprint 20 |
| Components | TiAPI |
| Labels | n/a |
| Reporter | Ingo Muschenetz |
| Assignee | Opie Cyrus |
| Created | 2012-10-02T03:02:01.000+0000 |
| Updated | 2018-08-06T17:49:11.000+0000 |
Description
Add a method to Titanium.UI.WebView API to ignore invalid SSL certificate just like Titanium.Network.HTTPClient.setValidatesSecureCertificate(Boolean validatesSecureCertificate)
PR opened: https://github.com/appcelerator/titanium_mobile/pull/3116 Test case: " var webview = Titanium.UI.createWebView({url: 'https://www.mjvmobile.com.br', ignoreSslError: false}); var window = Titanium.UI.createWindow(); window.add(webview); window.open({modal:true}); " Make sure to test with true / false values along with the ignoreSslError property missing completely (should default to false behavior). When the value is true, the page should load. When the value is false or missing the page should not load and you can see a error logged in logcat.
This isn't documented. Any reason for that?
User error. The original PR added a new property, but failed to include a YAML update -- a big no-no. Note that as far as I can tell, it is _only_ supported on Android. Perhaps someone figured they'd put it off until the property was in parity across platforms... But even so, we should've had a doc bug opened to track it.
Cleaning up older fixed issues. If this issue should not have been closed as fixed, please reopen.