[TIMOB-2484] iOS: Httpclient ssl problem without different port
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Medium |
Status | Closed |
Resolution | Needs more info |
Resolution Date | 2012-04-30T11:20:47.000+0000 |
Affected Version/s | Release 1.8.2 |
Fix Version/s | n/a |
Components | iOS |
Labels | SupportTeam, api |
Reporter | Micky |
Assignee | Stephen Tramer |
Created | 2011-04-15T03:20:59.000+0000 |
Updated | 2017-03-16T20:40:51.000+0000 |
Description
If I put a port 443 or a different one the connection does not work
Comments
- Jeroen K. 2011-04-15
I can confirm that this doesn't work.
var xhr = Titanium.Network.createHTTPClient(); xhr.open('POST', 'https://someurl:2343');
throws an xhr.onerror:
{ error = "Error Domain=ASIHTTPRequestErrorDomain Code=1 \"A connection failure occurred\" UserInfo=0x6c21d80 {NSUnderlyingError=0x6c1ac70 \"The operation couldn\U2019t be completed. (kCFErrorDomainCFNetwork error 2.)\", NSLocalizedDescription=A connection failure occurred}"; source = "[object TiNetworkClient]"; type = error; }
- Pedro Enrique 2011-05-10
We have a helpdesk ticket (TTR-59568-869) that is having a similar 443 problem that is probably also caused by this bug. Since they are using a local server, I have no way to test it myself, but the error is the following:
[ERROR] webserviceUtil.onerror: Error Domain=ASIHTTPRequestErrorDomain Code=1 "A connection failure occurred: SSL problem (possibly a bad/expired/self-signed certificate)" UserInfo=0x6d20150 {NSUnderlyingError=0x6d1fe00 "The operation couldn’t be completed. (OSStatus error -9807.)", NSLocalizedDescription=A connection failure occurred: SSL problem (possibly a bad/expired/self-signed certificate)}
- Stephen Tramer 2012-04-09 We require that all SSL bugs reported with HTTPClient first use TLS versioning to check and see if that resolves the issue. Please see the documentation for [Titanium.Network.TLSVersion](http://developer.appcelerator.com/apidoc/mobile/latest/Titanium.Network.HTTPClient.tlsVersion-property.html).
- Stephen Tramer 2012-04-30 We did not ever receive the following, which are required to resolve the ticket: * A complete working sample demonstrating the bug * Proof that the issue is not solved by setting Ti.Network.HTTPClient.tlsVersion to a specific value Marking this ticket as NEEDSMOREINFO as a result. If the requested information is supplied, we can reopen the ticket.
- Lee Morris 2017-03-16 Closing ticket as the information that was requested was never provided.