Hi all,
The byterange filter currently assumes that none of the content
generators or filters upstream is capable of handling range requests
themselves. As a result the filter will try to do a byterange on a
byterange.
The attached patch tells the byterange filter to back off if there
already is a content-type of multipart/byteranges.
Regards,
Graham
--
-----------------------------------------
[EMAIL PROTECTED] "There's a moon
over Bourbon Street
tonight..."
--- http_protocol.c-orig Fri Apr 13 05:43:29 2001
+++ http_protocol.c Mon Apr 16 13:45:16 2001
@@ -2347,6 +2347,12 @@
if (r->assbackwards)
return 0;
+ if ((ct = apr_table_get(r->headers_in, "Content-Type")) &&
+ (!strncasecmp(ct, "multipart/byteranges", 20) ||
+ !strncasecmp(ct, "multipart/x-byteranges", 22))) {
+ return 0;
+ }
+
/* Check for Range request-header (HTTP/1.1) or Request-Range for
* backwards-compatibility with second-draft Luotonen/Franks
* byte-ranges (e.g. Netscape Navigator 2-3).
