Mailing-List: contact dev-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpComponents Project" <dev@hc.apache.org>
Date: Thu, 6 Oct 2016 14:57:20 +0000 (UTC)
From: "Oleg Kalnichevski (JIRA)" <jira@apache.org>
To: dev@hc.apache.org
Message-ID: <JIRA.13009495.1475577884000.753659.1475765840600@Atlassian.JIRA>
In-Reply-To: <JIRA.13009495.1475577884000@Atlassian.JIRA>
References: <JIRA.13009495.1475577884000@Atlassian.JIRA> <JIRA.13009495.1475577884686@arcas>
Subject: [jira] [Updated] (HTTPCLIENT-1776) Handling of HEAD responses
 without payload headers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Thu, 06 Oct 2016 14:57:22 -0000


     [ https://issues.apache.org/jira/browse/HTTPCLIENT-1776?page=3Dcom.atl=
assian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oleg Kalnichevski updated HTTPCLIENT-1776:
------------------------------------------
    Summary: Handling of HEAD responses without payload headers  (was: Hand=
ling of HEAD without payload headers)

> Handling of HEAD responses without payload headers
> --------------------------------------------------
>
>                 Key: HTTPCLIENT-1776
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-177=
6
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: HttpClient (classic)
>    Affects Versions: 4.5.2
>            Reporter: Reinhold Fr=C3=BCsmer
>             Fix For: 5.0 Alpha2
>
>         Attachments: tomcat-squid-ntlm-not-stateful.pcapng, tomcat-squid-=
ntlm-stateful.pcapng, wire-context-log.txt, wirelog-4.5.3.txt
>
>
> Hi,
> I'm not sure if this is a problem with HttpClient itself or with Squid (3=
.3.8) proxy server, but maybe you could please advise.
> Our client application first sends a HEAD request for NTLM authentication=
 with the proxy and then re-uses the execution context as described in http=
s://hc.apache.org/httpcomponents-client-ga/tutorial/html/authentication.htm=
l for the following POST requests.
> Using more recent versions of Tomcat on the server-side, re-using the exe=
cution context does not work anymore, the NTLM authentication negotiate-cha=
llenge is repeated forever and following POST requests with chunked transfe=
r-encoding don't work  since they are interrupted by the authentication cha=
llenge.
> I figured out the difference betweeen newer and older Tomcat versions and=
 found the reason: previously, Tomcat automatically added a "Content-Length=
: 0" header to the reponse of HEAD requests. With "Bug 59310 - Content-Leng=
th of HEAD requests incorrectly computed as 0" (https://bz.apache.org/bugzi=
lla/show_bug.cgi?id=3D59310), this behavior was changed and without this he=
ader,  NTLM connections to the proxy don't persist anymore.=20
> As the content-length header is optional in a response to a HEAD request =
(RFC 7230), the problem must be either in HttpClient or Squid proxy.=20
> Thanks in advance!
> Best regards
> Reinhold=20


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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