Add a note on the overall problem with HEAD requests generating wrong headers.

Again, I believe this is a showstopper, but no one seems to agree with me.

Point at patch for 500/501 problem - I don't plan on testing or committing it.

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

diff --git a/STATUS b/STATUS
index 54e2a0981cfca720ca1fad9bd937782267df597f..ccbb6330f8f1e911798b95ed9a000091c665cad5 100644 (file)
--- a/STATUS
+++ b/STATUS
@@ -1,5 +1,5 @@
 APACHE 2.0 STATUS:                                              -*-text-*-
-Last modified at [$Date: 2002/06/13 18:07:58 $]
+Last modified at [$Date: 2002/06/13 18:37:00 $]
 
 Release:
 
@@ -94,9 +94,17 @@ CURRENT VOTES:
 
 RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
 
+    * All handlers should always send content down even if r->header_only
+      is set.  If not, it means that the HEAD requests don't generate the
+      same headers as a GET which is wrong.
+      Is this a showstopper?
+        +1: Justin
+        -1: 
+
     * 500 returned instead of 501 if a handler other than default_handler
       is invoked on a method with M_INVALID.
       Message-ID: <20020613001913.J22524@apache.org>
+      Proposed patch: <20020613111913.S22524@apache.org>
       Is this a showstopper?
         +1: Justin
         -1: Cliff, Aaron