[
https://issues.apache.org/jira/browse/HTTPCLIENT-1208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398468#comment-13398468
]
Oleg Kalnichevski commented on HTTPCLIENT-1208:
-----------------------------------------------
Do the requests share the same HTTP context? If they do not, how should
HttpClient know they belong to the same user or are in the same security
context?
Oleg
> PoolingClientConnectionManager give a new route even if keep-alive
> ------------------------------------------------------------------
>
> Key: HTTPCLIENT-1208
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1208
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient
> Affects Versions: 4.2 Final
> Reporter: restonica
>
> A connection is kept with a route and a specific state, for example :
> Connection [id: 0][route: {s}->https://x.x.x.x:8443][state: CN=KeyPair,
> OU=OU, O=O, L=Marseille, C=FR] can be kept alive for 30000 MILLISECONDS
> If a new connection with the same route is asked, for example:
> Connection request: [route: {s}->https://x.x.x.x:8443][total kept alive: 1;
> route allocated: 1 of 50; total allocated: 1 of 200]
> then the connection manager will give a NEW route (with a new ID).
> If the first kept connection (see the beginning) does not contain the state,
> all is OK and the connection manager give the same route as the previous one.
> This bug cause problem in case of SSL mutual authentication, a new TCP
> connection is done for each request !!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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]
