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] [Commented] (HTTPCORE-318) DefaultConnectionReuseStrategy -- need to honor keep alives when receiving a 404 on a HEAD request
Date Mon, 15 Oct 2012 11:16:03 GMT

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

Oleg Kalnichevski commented on HTTPCORE-318:

I cannot I speak for HTTPD developers. Apparently they know a great deal more about upcoming
HTTP protocol changes than I. I can only tell you how server side protocol handlers in HttpCore
implement GET request processing. RFC 2616 is actually pretty clear as to how HEAD should
be implemented: HEAD method is identical to HEAD except it may not contain a content body
(RFC2616, section 9.4). The server must generate _identical_ meta-information in the response
as if they were GET requests and strip the content body. That is precisely what HttpCore server
side protocol handlers do. Message meta-information clearly includes Content-Length (RFC2616,
section 7.1).

If you happen to have some spare cycles it would be an enormous service to all HTTPD users
if you could approach HTTPD developers and find out why on earth the newer versions HTTPD
deviate from RFC 2616 (which is _the_ official HTTP spec) with regards to HEAD method handling.

> 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

View raw message