hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Fitzhenry (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HTTPCORE-318) DefaultConnectionReuseStrategy -- need to honor keep alives when receiving a 404 on a HEAD request
Date Tue, 31 May 2016 15:17:13 GMT

    [ https://issues.apache.org/jira/browse/HTTPCORE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15307895#comment-15307895
] 

Tom Fitzhenry commented on HTTPCORE-318:
----------------------------------------

Since this is not yet available in a stable release, here is how I worked around this for
httpasyncclient 4.1.1, without having to fork/patch httpclient: https://gist.github.com/tomfitzhenry/159b793bce9e4da4ad3c13aede869d5c


> DefaultConnectionReuseStrategy -- need to honor keep alives when receiving a 404 on a
HEAD request
> --------------------------------------------------------------------------------------------------
>
>                 Key: HTTPCORE-318
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-318
>             Project: HttpComponents HttpCore
>          Issue Type: Improvement
>          Components: HttpCore
>    Affects Versions: 4.2.2
>            Reporter: Jon Christiansen
>             Fix For: 5.0-alpha1
>
>
> Code will not allow connection reuse if Content-Length header is not present.
> If the request was a HEAD request and the response is a 404, this header is not present,
but HttpClient should still be able to re-use the connection.
> It should be very easy to add special case code when dealing with responses to HEAD requests.



--
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


Mime
View raw message