[
https://issues.apache.org/jira/browse/HTTPCLIENT-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325874#comment-14325874
]
Ivan Shcheklein commented on HTTPCLIENT-1522:
---------------------------------------------
I didn't say that DefaultHttpClientConnectionOperator leaks. I said "it's not
obvious that connect call is idempotent" and "this code doesn't leak". I mean
that it's not obvious that it is safe to call connect twice with the same
parameters.
For example, we call it with the same ManagedHttpClientConnection instance.
Second call binds new socket to it:
{code:java}
Socket sock = sf.createSocket(context);
...
conn.bind(sock);
{code}
What has happened to the first one? I don't know where and when close is called.
> SNI support
> -----------
>
> Key: HTTPCLIENT-1522
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1522
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient
> Affects Versions: 4.3.4
> Reporter: Igor
>
> Running HttpRequest to https://touchpoint.tealeaveshealth.com/consume
> causes an error
> {code}
> javax.net.ssl.SSLProtocolException: handshake alert: unrecognized_name
> {code}
> to see how to fix, you can open
> *http://stackoverflow.com/questions/7615645/ssl-handshake-alert-unrecognized-name-error-since-upgrade-to-java-1-7-0*
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
