You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2017/10/28 04:03:00 UTC

[jira] [Resolved] (DIRMINA-844) Http Proxy Authentication failed to complete (see description for exact point of failure)

     [ https://issues.apache.org/jira/browse/DIRMINA-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny resolved DIRMINA-844.
---------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 2.0.8)
                   2.0.17

Patch applied : http://git-wip-us.apache.org/repos/asf/mina/commit/0d8e4038

Thanks a lot !

> 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
>             Fix For: 2.0.17
>
>
> 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 was sent by Atlassian JIRA
(v6.4.14#64029)