[
https://issues.apache.org/jira/browse/HTTPASYNC-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13157497#comment-13157497
]
Oleg Kalnichevski commented on HTTPASYNC-9:
-------------------------------------------
I need to rethink the whole concept of secure session demarcation. Please bear
with me.
Oleg
> SSL issue related to logging
> ----------------------------
>
> Key: HTTPASYNC-9
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-9
> Project: HttpComponents HttpAsyncClient
> Issue Type: Bug
> Affects Versions: 4.0-alpha3
> Reporter: Rosen Anastasov
> Fix For: 4.0-alpha4
>
>
> The ManagedAsyncClientConnectionImpl decides if a route is secure with the
> following check:
> conn.getIOSession() instanceof SSLIOSession
> But depending on the log level the session will be either SSLIOSession (debug
> level lower than DEBUG) or LoggingIOSession (debug level DEBUG or higher).
> And since the LoggingIOSession is not instanceof SSLIOSession - the check is
> invalid. This effectively disables the HTTPS connections as the AsyncClient
> is unable to create route to the destination.
--
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]
