[
https://issues.apache.org/jira/browse/HTTPCLIENT-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325854#comment-14325854
]
Oleg Kalnichevski commented on HTTPCLIENT-1522:
-----------------------------------------------
bq. it's far from obvious DefaultHttpClientConnectionOperator::connect is
idempotent. I'm still not 100% sure that this code doesn't leak socket in some
cases
What cases would that be? If you find DefaultHttpClientConnectionOperator
leaking sockets in any circumstances please let me know
bq. probably, it will be hard to maintain it
Welcome to the real world without any rfc-perfect illusions.
Oleg
> 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]
