Showstoppers and something not to be forgotten..

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

diff --git a/STATUS b/STATUS
index 6ffb9a43251ee54dc5e477f9d97cad8b16afc1f8..450f3aa1405a2df371ca92a98c1719868ae1197f 100644 (file)
--- a/STATUS
+++ b/STATUS
@@ -1,5 +1,5 @@
 APACHE 2.0 STATUS:                                             -*-text-*-
-Last modified at [$Date: 2001/12/15 18:32:29 $]
+Last modified at [$Date: 2001/12/17 22:05:58 $]
 
 Release:
 
@@ -39,6 +39,13 @@ on related projects:
 
 RELEASE SHOWSTOPPERS:
 
+    * Test suite failures:
+      o perchild doesn't even build
+      o all MPMs fail the LimitRequestBody directive test
+      o both worker and prefork are failing some of the 'chunked' subtests
+      o worker is also failing some of the 'cgi' subtests
+      (see <URL:http://Source-Zone.Org/Apache/regression/>):
+
     * If any request gets to the core handler, without a flag that this 
       r->filename was tested by dir/file_walk, we need to 500 at the very 
       end of the ap_process_request_internal() processing.  This provides
@@ -94,6 +101,19 @@ RELEASE SHOWSTOPPERS:
 
 RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
 
+    * Handling of %2f in URIs.  Currently both 1.3 and 2.0
+      completely disallow %2f in the request URI path (see
+      ap_unescape_url() in util.c).  It's permitted and passed
+      through in the query string, however.  Roy says the
+      original reason for disallowing it, from five years ago,
+      was to protect CGI scripts that applied PATH_INFO to
+      a filesystem location and which might be tricked by
+      ..%2f..%2f(...).  We *should* allow path-info of the
+      form 'http://foo.com/index.cgi/path/to/path%2finfo'.
+      Since we've revamped a lot of our processing of path
+      segments, it would be nice to allow this, or at least
+      allow it conditionally with a directive.
+
     * FreeBSD, threads, and worker MPM.  All seems to work fine 
       if you only have one worker process with many threads.  Add 
       a second worker process and the accept lock seems to be