[
https://issues.apache.org/jira/browse/HTTPCORE-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski resolved HTTPCORE-327.
----------------------------------------
Resolution: Invalid
This is in fact an expected behavior. By default HttpClient has not way of
knowing that requests are issued by the same user and it is OK to re-use user
specific connections for that. You need to tell HttpClient that requests
belong to the same session (user) by using the same execution context for
logically related requests. Alternatively, if you can choose to disable state
management for SSL connections but you need to be aware of security
implications of doing so.
Oleg
> SSL persistent connections with client certificates
> ---------------------------------------------------
>
> Key: HTTPCORE-327
> URL: https://issues.apache.org/jira/browse/HTTPCORE-327
> Project: HttpComponents HttpCore
> Issue Type: Bug
> Components: HttpCore
> Affects Versions: 4.2.3
> Reporter: Markus Woschank
>
> using httpclient (4.2.2) and httpcore (4.2.3) ssl connections to a server
> (https) requiring client certificates are not reused.
> i am using DefaultHttpClient and PoolingClientConnectionManager to execute
> the requests.
> traced it to:
> RouteSpecificPool:90 (getFree)
> > if (entry.getState() == null)
> it seems the pooled connection has a X500Principal attached whereas the
> method is called with state==null.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
