Vote, promote, comment

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x@667652 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/STATUS b/STATUS
index effe81f250564d8b5b1143865f8584c6988614b0..1b2612eb051045ac139511444d5193938eb6a8fc 100644 (file)
--- a/STATUS
+++ b/STATUS
@@ -83,6 +83,14 @@ RELEASE SHOWSTOPPERS:
 PATCHES ACCEPTED TO BACKPORT FROM TRUNK:
   [ start all new proposals below, under PATCHES PROPOSED. ]
 
+ * mod_authz_host: Also allow for negation of env-var (env=!)
+   for allow/deny criteria.
+   Trunk version of patch:
+         http://svn.apache.org/viewvc?view=rev&revision=667513
+   Backport version for 2.2.x of patch:
+         http://people.apache.org/~jim/patches/nenv-mod_authz_host.txt
+   +1: jim, rpluem, niq
+
 PATCHES PROPOSED TO BACKPORT FROM TRUNK:
   [ New proposals should be added at the end of the list ]
 
@@ -136,14 +144,10 @@ PATCHES PROPOSED TO BACKPORT FROM TRUNK:
    Backport version for 2.2.x of patch:
          Trunk version of patch works
    +1: jim, rpluem
-
- * mod_authz_host: Also allow for negation of env-var (env=!)
-   for allow/deny criteria.
-   Trunk version of patch:
-         http://svn.apache.org/viewvc?view=rev&revision=667513
-   Backport version for 2.2.x of patch:
-         http://people.apache.org/~jim/patches/nenv-mod_authz_host.txt
-   +1: jim, rpluem
+   niq: Interesting point in RFC2616: a client can send Expect to
+        a 1.0 server, but a proxy mustn't.  But I'm not convinced
+        by the use of force-proxy-request-1.0, when RFC2616 suggests
+        caching backend response headers.
 
 PATCHES/ISSUES THAT ARE STALLED