From 28aaf54224bdb222498430c42627f8f78b9f6a54 Mon Sep 17 00:00:00 2001 From: Rainer Jung Date: Mon, 1 Jun 2015 15:04:41 +0000 Subject: [PATCH] Prune resolved discussion, vote. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1682924 13f79535-47bb-0310-9956-ffa450edef68 --- STATUS | 15 +-------------- 1 file changed, 1 insertion(+), 14 deletions(-) diff --git a/STATUS b/STATUS index 340cf308f8..95da97491e 100644 --- a/STATUS +++ b/STATUS @@ -216,20 +216,7 @@ PATCHES PROPOSED TO BACKPORT FROM TRUNK: trunk patch: http://svn.apache.org/r1681694 trunk patch: http://svn.apache.org/r1682907 2.4.x patch: trunk works (modulo CHANGES) - +1: ylavic - rjung: Would it makes sense to handle 500/503 for the other proxy - protocols similar? I see error_override at least also in the - AJP and FCGI case. - ylavic: Done in r1682907 for AJP, FCGI calls ap_die() by itself and - thus always returns OK (hence the note is not needed). - rjung: What about setting the note proxy-error-override in general - if an error override happens so it might get more uses in - the future. Would that make sense? - ylavic: The note is always set by each (concerned) proxy module whenever - a backend error is returned to the handler (for any error status), - but we can't set it for "internal" errors (500/503) when - ProxyErrorOverride is configured because we want the handler to - take care of the balancer members (un)recovery state in this case. + +1: ylavic, rjung PATCHES/ISSUES THAT ARE BEING WORKED -- 2.40.0