Update mod_proxy-transfer patch to address Eric's concerns.

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

diff --git a/STATUS b/STATUS
index bcc4ee1fd144fa7c80e710939ab5b9f08ecfac49..54c3339780dd78172fb1ae5cd6698ccf66715012 100644 (file)
--- a/STATUS
+++ b/STATUS
@@ -311,11 +311,13 @@ PATCHES PROPOSED TO BACKPORT FROM TRUNK:
      side when none occurs next on the other side, and abort.
      trunk patch: http://svn.apache.org/r1657636
                   http://svn.apache.org/r1657638
-     2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-mod_proxy-transfer.patch
+                  http://svn.apache.org/r1669130
+     2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-mod_proxy-transfer-v2.patch
      +1: ylavic
      covener: I noticed while reviewing that rv is not used in ap_log_rerror at least
      in the path context. If it had, the |= would have dropped the strerror.  Think
      there's any risk in having rv like that floating around?
+     ylavic: Agreed, fixed in r1669130 (and v2) by using a pure boolean instead.
 
   *) mod_dav: Avoid a potential integer underflow in the lock timeout value sent
      back to a client. PR 55420