demote the Content-Range/416/SSI problem to non-showstopper.

It's been happening for ages, there are no PRs I'm aware of, and the core
dumps that happened as a side effect in 2.0.35 seem to be resolved.

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

diff --git a/STATUS b/STATUS
index 30088decf10600cbe2c43a1787cea0f31b63e855..db476e2b99b593cf4e6fed16571afaf628e7f9bc 100644 (file)
--- a/STATUS
+++ b/STATUS
@@ -1,5 +1,5 @@
 APACHE 2.0 STATUS:                                              -*-text-*-
-Last modified at [$Date: 2002/04/22 20:37:34 $]
+Last modified at [$Date: 2002/04/25 17:05:56 $]
 
 Release:
 
@@ -49,10 +49,6 @@ CURRENT RELEASE NOTES:
 
 RELEASE SHOWSTOPPERS:
 
-    * 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.
 
@@ -85,6 +81,10 @@ CURRENT VOTES:
 
 RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
 
+    * 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.
+
     * --enable-mods-shared="foo1 foo2" is busted on Darwin.  Pier
         posted a patch (Message-ID: <B8DBBE8D.575A%pier@betaversion.org>).