From: Graham Leggett <minfrin@apache.org>
Date: Fri, 10 Dec 2021 16:05:24 +0000 (+0000)
Subject: Withdraw stale proposal. Replacement patches have solved same problem
X-Git-Tag: candidate-2.4.52-rc1~72
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=1c41d8dc1ce71356a770c02cc3934fd701d6af6f;p=thirdparty%2Fapache%2Fhttpd.git

Withdraw stale proposal. Replacement patches have solved same problem
in a way that could be backported.


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

diff --git a/STATUS b/STATUS
index f03da280501..7f52755b868 100644
--- a/STATUS
+++ b/STATUS
@@ -274,23 +274,6 @@ PATCHES/ISSUES THAT ARE BEING WORKED
      +1: ylavic,
      ylavic: still being discussed on dev@
 
-  *) mod_dav: Allow other modules to become providers and add ACLs
-     to the DAV response.
-     trunk patch: http://svn.apache.org/r1748322
-                  http://svn.apache.org/r1824590
-                  http://svn.apache.org/r1824596
-     2.4.x: trunk works modulo CHANGES/MMN/log-message
-     +1: minfrin, jim
-     -1: rpluem: While we allow extensions of structures at the end in general
-                 this is a specific case where the the design of the mod_dav
-                 API clashes with this approach, as the API requires consumers
-                 to create the public structs on their own, something we do
-                 not "allow/encourage" otherwise in order to be able to do the
-                 structure extension. I don't want to see consumers of this API
-                 suffer from the clash we created.
-                 See also:
-                 https://lists.apache.org/thread.html/b924afe0fcc58a8636b753e630421bf6dc2080653a79575fd5fd641a@%3Cdev.httpd.apache.org%3E
-
   *) http: Don't remove the Content-Length of zero from a HEAD response if
      it comes from an origin server, module or script. Allow the previous
      behaviour (for legacy/buggy modules only, not origin) by also backporting