Http Proxy Authentication failed to complete (see description for exact point 
of failure)
-----------------------------------------------------------------------------------------

                 Key: DIRMINA-844
                 URL: https://issues.apache.org/jira/browse/DIRMINA-844
             Project: MINA
          Issue Type: Bug
          Components: Core
    Affects Versions: 2.0.3
         Environment: Mac OS X 10.6.8 
JDK 1.6
squid/2.6
Eclipse
            Reporter: Parijat Bansal


When trying to connect through an Squid Http Proxy using ProxyConnector 
(requiring basic authentication). While debugging issue, I walked through MINA 
code. Following are my observations:
1. First attempt made by MINA do not send any authentication details even 
though property set, seems like its to get first response mentioning 
authentication method. 
2. So a second connection is initiated from ProxyConnector and this time 
request contains the authentication header. 

ISSUE: My client kept waiting at this point and it seems that second connection 
never got completed. I used eclipse debugger and found that 
AbstractPollingIoConnector.connect0 method is getting called with proper 
destination (As I used a NioSocketConnector to construct ProxyConnector) but 
after that no progress.

Also  at Line#343 following were the content of request variable (I wonder if 
this could be of help )


request AbstractPollingIoConnector$ConnectionRequest  (id=82)   
        deadline        1310717009666   
        firstListener   null    
        handle  SocketChannelImpl  (id=88)      
        lock    AbstractPollingIoConnector$ConnectionRequest  (id=82)   
        otherListeners  null    
        ready   false   
        result  null    
        session null    
        sessionInitializer      ProxyIoSessionInitializer<T>  (id=104)  
        this$0  NioSocketConnector  (id=40)     
        waiters 0       


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to