[TIMOB-1025] Self-signed SSL certificates cause issues for HTTP Client (Android)
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Medium |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2011-04-17T01:54:59.000+0000 |
Affected Version/s | n/a |
Fix Version/s | Release 1.4.0 |
Components | Android |
Labels | android, defect, httpclient |
Reporter | Kevin Whinnery |
Assignee | Marshall Culpepper |
Created | 2011-04-15T02:41:46.000+0000 |
Updated | 2011-04-17T01:54:59.000+0000 |
Description
We have a community member reporting issues using self-signed SSL certificates (in this case, on a local dev server where he would be using such a cert). A quick Google search reveals that special gymnastics might be necessary to get self-signed certs to work in Android:
http://www.google.com/search?q=android+self-signed+SSL+certificate"> http://www.google.com/search?q=android+self-signed+SSL+certificate
Will update this ticket with an example ASAP.
Here is the trace the user is getting in Ti Developer:
http://pastie.org/974796">http://pastie.org/974796
This issue is a duplicate of #1167, and should be resolved as of this commit:
http://github.com/appcelerator/titanium_mobile/commit/10616aaffcbebcddcc8a3d4f5123d2351666929a"> http://github.com/appcelerator/titanium_mobile/commit/10616aaffcbeb...
rollback wrong update