From: Greg Ames <gregames@apache.org>
Date: Mon, 22 Apr 2002 20:37:34 +0000 (+0000)
Subject: Clarify the remaining problems with Range: headers.  The seg faults went away
X-Git-Tag: 2.0.36~117
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=2e9b9fa8f09c39e609a695f7217ae408386f4304;p=thirdparty%2Fapache%2Fhttpd.git

Clarify the remaining problems with Range: headers.  The seg faults went away
when we changed ap_send_error_response to get rid of resource filters.

This was triggered because we generate a lot of invalid 416 responses for SSI.
That happens because the complete length of the entity body (response) isn't
known accurately until after the C/L filter runs.  That's C/L's job, after all.

Flipping the order of the byterange and C/L filters fixes the invalid
Content-Range headers and 416's.  But then the Content-Length header contains
the full length, rather than the sum of the returned ranges.  That's wrong, but
doesn't seem too hard to fix.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@94762 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/STATUS b/STATUS
index 02b0ec29a9c..30088decf10 100644
--- a/STATUS
+++ b/STATUS
@@ -1,5 +1,5 @@
 APACHE 2.0 STATUS:                                              -*-text-*-
-Last modified at [$Date: 2002/04/22 19:41:41 $]
+Last modified at [$Date: 2002/04/22 20:37:34 $]
 
 Release:
 
@@ -49,8 +49,9 @@ CURRENT RELEASE NOTES:
 
 RELEASE SHOWSTOPPERS:
 
-    * Is there still a C-L / byterange filter misordering problem?
-      If so, do any patches exist?
+    * Incorrect Content-Range headers or invalid 416 HTTP responses
+      if a filter such as INCLUDES changes the content length.  It may
+      happen only when there are multiple output brigades.
 
     * worker MPM segfaults because the apr_bucket_alloc_t is cleaned
       up twice.