hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HTTPCORE-434) Handling of HEAD responses without payload headers
Date Sat, 08 Oct 2016 11:19:20 GMT

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

Oleg Kalnichevski resolved HTTPCORE-434.
    Resolution: Fixed

Fixed in SVN trunk and 4.4.x branch. Please verify the fix and close.


> Handling of HEAD responses without payload headers
> --------------------------------------------------
>                 Key: HTTPCORE-434
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-434
>             Project: HttpComponents HttpCore
>          Issue Type: Bug
>          Components: HttpCore
>    Affects Versions: 4.4.5
>            Reporter: Reinhold Früsmer
>             Fix For: 4.4.6, 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 https://hc.apache.org/httpcomponents-client-ga/tutorial/html/authentication.html
for the following POST requests.
> Using more recent versions of Tomcat on the server-side, re-using the execution context
does not work anymore, the NTLM authentication negotiate-challenge is repeated forever and
following POST requests with chunked transfer-encoding don't work  since they are interrupted
by the authentication challenge.
> 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-Length of HEAD requests incorrectly computed as 0" (https://bz.apache.org/bugzilla/show_bug.cgi?id=59310),
this behavior was changed and without this header,  NTLM connections to the proxy don't persist
> 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. 
> Thanks in advance!
> Best regards
> Reinhold 

This message was sent by Atlassian JIRA

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

View raw message