[
https://issues.apache.org/jira/browse/HTTPCLIENT-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325659#comment-14325659
]
Oleg Kalnichevski commented on HTTPCLIENT-1522:
-----------------------------------------------
bq. Let's face it - we need http client to work with real world, not with some
rfc-perfect illusion
That's precisely why one can plug in custom code into HC.
bq. Probably it's not a bug, but it looks like a problem in socket creation
architecture. Probably it should be located in one place to be easily accessed
by descendants.
I think SNI recovery logic should be moved from CustomSSLSocketFactory to a
custom HttpClientConnectionOperator implementation. You can still pass some
contextual details to the socket factory through HttpContext if necessary.
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]
