You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Rosen Anastasov (Created) (JIRA)" <ji...@apache.org> on 2011/11/15 10:29:52 UTC

[jira] [Created] (HTTPASYNC-9) SSL issue related to logging

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


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: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


[jira] [Commented] (HTTPASYNC-9) SSL issue related to logging

Posted by "Andy (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HTTPASYNC-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13157361#comment-13157361 ] 

Andy commented on HTTPASYNC-9:
------------------------------

Actaully, DefaultAsyncClientConnection shoud make sure return the raw IOSession on getIOSession rather than a wrapped LogginIOSession object.
                
> 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: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


[jira] [Updated] (HTTPASYNC-9) SSL issue related to logging

Posted by "Oleg Kalnichevski (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HTTPASYNC-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oleg Kalnichevski updated HTTPASYNC-9:
--------------------------------------

    Fix Version/s: 4.0-alpha4
    
> 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: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


[jira] [Resolved] (HTTPASYNC-9) SSL issue related to logging

Posted by "Oleg Kalnichevski (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HTTPASYNC-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oleg Kalnichevski resolved HTTPASYNC-9.
---------------------------------------

    Resolution: Fixed

Fixed in SVN trunk.

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-beta1
>
>
> 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: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


[jira] [Commented] (HTTPASYNC-9) SSL issue related to logging

Posted by "Oleg Kalnichevski (Commented) (JIRA)" <ji...@apache.org>.
    [ 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: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org