You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Jon Christiansen (JIRA)" <ji...@apache.org> on 2012/10/15 05:37:02 UTC
[jira] [Commented] (HTTPCORE-318) DefaultConnectionReuseStrategy --
need to honor keep alives when receiving a 404 on a HEAD request
[ https://issues.apache.org/jira/browse/HTTPCORE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475945#comment-13475945 ]
Jon Christiansen commented on HTTPCORE-318:
-------------------------------------------
Just curious, if you were the Apache HTTPd developer responsible for programming to correctly respond for this case, how would you implement this? If you were going to actually return a Content-Length header on the 404 response to a HEAD, what value would you use? How would you derive the value?
> 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: Future
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org