Start tracking the PRs for known RFC 2616 violations. (Note that the test

cases in the PR are ridiculously hard to follow.)

These tend to be primarily in caching/proxy, but some are in the core.

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

diff --git a/STATUS b/STATUS
index 7bbfee3c1d9205911f1c094e767f0030bf66436c..c643e635c9b3c14b23e34933cb9a61b91273d69f 100644 (file)
--- a/STATUS
+++ b/STATUS
@@ -1,5 +1,5 @@
 APACHE 2.1 STATUS:                                              -*-text-*-
-Last modified at [$Date: 2003/02/18 21:06:15 $]
+Last modified at [$Date: 2003/02/19 07:21:43 $]
 
 Release [NOTE that only Alpha/Beta releases occur in 2.1 development]:
 
@@ -75,6 +75,14 @@ CURRENT VOTES:
 
 RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
 
+    * RFC 2616 violations.
+      Closed PRs: 15857.
+      Open PRs: 15852, 15859, 15861, 15864, 15865, 15866, 15868, 15869,
+                15870, 16120, 16125, 16126, 16133, 16135, 16136, 16137,
+                16138, 16139, 16140, 16142, 16518, 16520, 16521, 
+      jerenkrantz says: need to decide how many we need to backport and/or
+                        if these rise to showstopper status.
+
     * There is a bug in how we sort some hooks, at least the pre-config
       hook.  The first time we call the hooks, they are in the correct 
       order, but the second time, we don't sort them correctly.  Currently,