From 1161f94b7ecce7cb0ba0b74aac89c79f373c0905 Mon Sep 17 00:00:00 2001 From: Yann Ylavic Date: Wed, 25 Mar 2015 16:04:11 +0000 Subject: [PATCH] Update mod_proxy-transfer patch to v3 (v2 was missing APR_EBADF case). git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1669141 13f79535-47bb-0310-9956-ffa450edef68 --- STATUS | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/STATUS b/STATUS index 54c3339780..9e4294d37b 100644 --- a/STATUS +++ b/STATUS @@ -312,12 +312,12 @@ PATCHES PROPOSED TO BACKPORT FROM TRUNK: trunk patch: http://svn.apache.org/r1657636 http://svn.apache.org/r1657638 http://svn.apache.org/r1669130 - 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-mod_proxy-transfer-v2.patch + 2.4.x patch: http://people.apache.org/~ylavic/httpd-2.4.x-mod_proxy-transfer-v3.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. + ylavic: Agreed, fixed in r1669130 (and v3) 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 -- 2.50.1