Where mod_proxy_http has a code path for allowing Apache it's own ErrorDocument should a remote server return, say, a 404, mod_proxy_ajp has no such code path, which forces one to use the back-end's error pages, which may not be what's desired.
Created attachment 23333 [details] Initial (though perhaps not complete) patch Attached is an initial patch that provides this functionality. It may not be complete (e.g. it doesn't do any special handling for 401 like mod_proxy_http does), and I make no claims to be an expert in the Apache code, so it may not be complete or 100% correct. That said, though, I have been using this patch for some time with no issues.
Will someone please look into the proposed patch??
This should at least be mentioned in the documentation. 2.3.11-beta source looks like the bug still exists in 2.3, too.
It looks like this has been fixed in 50945. *** This bug has been marked as a duplicate of bug 50945 ***