Mailing-List: contact dev-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpComponents Project" <dev@hc.apache.org>
Date: Fri, 17 Mar 2017 15:52:41 +0000 (UTC)
From: "Karl Wright (JIRA)" <jira@apache.org>
To: dev@hc.apache.org
Message-ID: <JIRA.13057045.1489765165000.50565.1489765961572@Atlassian.JIRA>
In-Reply-To: <JIRA.13057045.1489765165000@Atlassian.JIRA>
References: <JIRA.13057045.1489765165000@Atlassian.JIRA> <JIRA.13057045.1489765165940@jira-lw-us.apache.org>
Subject: [jira] [Assigned] (HTTPCLIENT-1833) RuntimeException from
 WindowsNegotiateScheme: Unexpected token
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 17 Mar 2017 15:52:48 -0000


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

Karl Wright reassigned HTTPCLIENT-1833:
---------------------------------------

    Assignee: Karl Wright

> RuntimeException from WindowsNegotiateScheme: Unexpected token
> --------------------------------------------------------------
>
>                 Key: HTTPCLIENT-1833
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1833
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>    Affects Versions: 4.5.3
>         Environment: Client: Windows 8.1, Proxy: Squid 3.5.20 on Centos 7.0
>            Reporter: Antony Helliwell
>            Assignee: Karl Wright
>
> We have a test setup using Squid 3.5.20 as an authenticating proxy configured with NEGOTIATE+NTLM.  When attempting to connect to a target host we get the following traceback:
> java.lang.RuntimeException: Unexpected token
> 	at org.apache.http.impl.auth.win.WindowsNegotiateScheme.parseChallenge(WindowsNegotiateScheme.java:152)
> 	at org.apache.http.impl.auth.AuthSchemeBase.processChallenge(AuthSchemeBase.java:126)
> 	at org.apache.http.impl.auth.HttpAuthenticator.handleAuthChallenge(HttpAuthenticator.java:137)
> 	at org.apache.http.impl.execchain.MainClientExec.needAuthentication(MainClientExec.java:579)
> 	at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:293)
> 	at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185)
> 	at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
> 	at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:111)
> 	at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
> 	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
> 	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56)
> 	...
> I've tracked this down to WindowsNegotiateScheme using the SPN  HTTP/<target host name> to authenticate with the proxy rather than the SPN HTTP/<proxy host name>.
> Applying https://github.com/apache/httpclient/pull/28 fixes the problem. 
> The request is from early 2015 and doesn't seem to have been applied due to a pending rewrite, however the bug still exists at 4.5.3. 


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org