Am 01.06.2015 um 13:36 schrieb Yann Ylavic:
Hi Rainer,
On Mon, Jun 1, 2015 at 1:06 PM, <rj...@apache.org> wrote:
@@ -232,14 +238,14 @@ PATCHES PROPOSED TO BACKPORT FROM TRUNK:
trunk patch: http://svn.apache.org/r1681694
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.
I'll have a look at these, looks consitent to do it there too.
+ 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?
I'm not sure to understand here, what would be a "general" way to set the note?
It seems to me that each (proxy) module only can tell whether the
error comes from itself or the backend.
I meant "set it always if a ProxyErrorOverride happens", not "set it if
we need it for the 500/503 check later". Maybe this is (for http)
already the case, not sure about possible code paths for ProxyErrorOverride.
Rainer
