From: Luca Toscano Date: Sun, 5 Jul 2020 17:31:56 +0000 (+0000) Subject: STATUS: move proposal from being worked to backport [skip ci] X-Git-Tag: 2.4.44~43 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=332852f22b1b6c6503f0647be39b189dee5d6790;p=thirdparty%2Fapache%2Fhttpd.git STATUS: move proposal from being worked to backport [skip ci] This change seems ready again for another round of review/discussion, to see if it is ok to backport or if it needs more work (or even a revert). The goal is to reduce the amount of code in review, to reduce the diff between trunk and 2.4.x. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1879534 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/STATUS b/STATUS index cc4a906e3bb..a03dec9d0d2 100644 --- a/STATUS +++ b/STATUS @@ -245,27 +245,6 @@ PATCHES PROPOSED TO BACKPORT FROM TRUNK: 2.4.x patch https://svn.apache.org/repos/asf/httpd/httpd/patches/2.4.x/httpd-etag1.patch +1: minfrin - -PATCHES/ISSUES THAT ARE BEING WORKED - [ New entries should be added at the START of the list ] - - *) 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 - *) core: Drop an invalid Last-Modified header value coming from a (F)CGI script instead of replacing it with Unix epoch. Warn the users about Last-Modified header value replacements @@ -283,11 +262,6 @@ PATCHES/ISSUES THAT ARE BEING WORKED 2.4.x: trunk patches work, final view: http://home.apache.org/~elukey/httpd-2.4.x-core-last_modified_tz_logging.patch svn merge -c 1748379,1750747,1750749,1750953,1751138,1751139,1751139,1757818,1879253,r1879348 ^/httpd/httpd/trunk . - The problem has been discussed in dev@ extensively but we did not reach a common - agreement about how to proceed in the long term. While we wait, I would really like - to introduce useful logs for the users (the starting point of this change was a users@ - email thread). If this is not the right way to go I will move the patch to other - sections of STATUS (stalled or being worked). The code has been tested with a simple PHP script returning different Last-Modified headers (GMT now, GMT now Europe/Paris, GMT tomorrow, GMT yesterday, PST now). +1: elukey, jorton @@ -295,8 +269,27 @@ PATCHES/ISSUES THAT ARE BEING WORKED rather than "silently" (at normal log-level) dropping the parsed header? [also nit: wrapping a lone ap_log_rerror(,APLOG_X) call in if (APLOGrX(..) is unnecessary/redundant] - elukey: Hopefully fixed the suggestions made with r1879253, let me know if this change - can go back to the proposed section (leaving the being worked one). + + +PATCHES/ISSUES THAT ARE BEING WORKED + [ New entries should be added at the START of the list ] + + *) 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