- for multipart byterange responses we should not send Content-Length

  until we can calculate it.

diff --git a/TODO b/TODO
index a1413f105bac9e0304a7773592732dd6a3b7c378..14670ba94cb4341424cd4d084d7a79b373dfe2b4 100644 (file)
--- a/TODO
+++ b/TODO
@@ -15,6 +15,7 @@ Our Todo List
                - An orderd list of siblings to try.  
                - Hash function load balancing
 (2)    Track cache keys (MD5) in memory utilization
+(2)     Calculate Content-Length for multipart range replies (AR)
 
 (3)    hit metering
 (3)    ETag support (makes metadata bigger--ack!)

diff --git a/src/client_side.cc b/src/client_side.cc
index bb3fd86a6db1c4832406ded70a4b8c4bdc13e9ec..29c618bc1ab09ad4466568c0f9a9635d28aa8c96 100644 (file)
--- a/src/client_side.cc
+++ b/src/client_side.cc
@@ -1,6 +1,6 @@
 
 /*
- * $Id: client_side.cc,v 1.351 1998/07/15 23:59:07 wessels Exp $
+ * $Id: client_side.cc,v 1.352 1998/07/16 00:18:52 rousskov Exp $
  *
  * DEBUG: section 33    Client-side Routines
  * AUTHOR: Duane Wessels
@@ -1016,6 +1016,9 @@ clientBuildRangeHeader(clientHttpRequest * http, HttpReply * rep)
                "multipart/byteranges; boundary=\"%s\"",
                strBuf(http->range_iter.boundary));
            /* no need for Content-Length in multipart responses */
+           /* but we must delete the original one if we cannot (yet)
+            * calculate the actual length */
+           httpHeaderDelById(hdr, HDR_CONTENT_LENGTH);
        }
     }
 }