Author: Alex Rousskov <rousskov@measurement-factory.com>

HTTP Compliance: do not remove ETag header from partial responses

RFC 2616 section 10.2.7 says that partial responses MUST include ETag
header if it would have been sent in a 200 response to the same request.

Co-Advisor test cases:
    test_case/rfc2616/scHdrs-206-include-explicit-withVary-noIfs
    test_case/rfc2616/scHdrs-206-include-explicit-woutVary-noIfs
    test_case/rfc2616/scHdrs-206-include-other-If-Range-strong

diff --git a/src/client_side.cc b/src/client_side.cc
index d6576489e9180cab807dec4647dd9bebbd47ca10..9326ee45a3ca560c9301c601459d6d4c15b34bb1 100644 (file)
--- a/src/client_side.cc
+++ b/src/client_side.cc
@@ -1161,8 +1161,6 @@ ClientSocketContext::buildRangeHeader(HttpReply * rep)
         debugs(33, 3, "clientBuildRangeHeader: range spec count: " <<
                spec_count << " virgin clen: " << rep->content_length);
         assert(spec_count > 0);
-        /* ETags should not be returned with Partial Content replies? */
-        hdr->delById(HDR_ETAG);
         /* append appropriate header(s) */
 
         if (spec_count == 1) {