Bug 50732 - Make ProxyErrorOverride configurable per status code
Summary: Make ProxyErrorOverride configurable per status code
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_proxy (show other bugs)
Version: 2.2.17
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2011-02-08 06:15 UTC by Peter
Modified: 2018-11-07 21:09 UTC (History)
0 users

samsung i phone gt c 3520 (27 bytes, text/plain)
2012-09-22 13:18 UTC, salbegorudy

Note You need to log in before you can comment on or make changes to this bug.
Description Peter 2011-02-08 06:15:10 UTC
I think it would be nice to be able to configure ProxyErrorOverride per http status code (4xx, 5xx) like:

ProxyErrorOverride 404 On
ProxyErrorOverride 500 Off
ProxyErrorOverride 403 Off

In this way you much more possibilities to configure how you should present error messages in a reverse proxy environment.

Best regards,

Comment 1 Peter 2011-07-01 07:14:54 UTC
Since 2.2 is not developed anymore I have filed this enhancement request against 2.4.

Best regards,

Comment 2 salbegorudy 2012-09-22 13:18:32 UTC
Created attachment 29406 [details]
samsung i phone gt c 3520

download free app jar
Comment 3 Christophe JAILLET 2018-05-29 05:20:48 UTC
Comment on attachment 29406 [details]
samsung i phone gt c 3520

hide spam attachment
Comment 4 William A. Rowe Jr. 2018-11-07 21:09:11 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.