[
https://issues.apache.org/jira/browse/DIRMINA-844?focusedWorklogId=237219&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-237219
]
ASF GitHub Bot logged work on DIRMINA-844:
------------------------------------------
Author: ASF GitHub Bot
Created on: 04/May/19 15:35
Start Date: 04/May/19 15:35
Worklog Time Spent: 10m
Work Description: asfgit commented on pull request #8: FIX DIRMINA-844
Http Proxy Authentication failed to complete
URL: https://github.com/apache/mina/pull/8
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 237219)
Time Spent: 10m
Remaining Estimate: 0h
> 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
> Priority: Major
> Fix For: 2.0.17
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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
(v7.6.3#76005)
