Bug 34377 - Allow the overriding of 401 Unauthorized returns from an origin server.
Summary: Allow the overriding of 401 Unauthorized returns from an origin server.
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_proxy (show other bugs)
Version: 2.1-HEAD
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL: http://primero.ricilake.net/proxy21.p...
Keywords: MassUpdate, PatchAvailable
Depends on:
Reported: 2005-04-08 20:43 UTC by Rici Lake
Modified: 2018-11-07 21:08 UTC (History)
0 users

Patch for mod_proxy.c to implement ProxyAuthOverride (3.28 KB, patch)
2005-04-08 20:45 UTC, Rici Lake
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Rici Lake 2005-04-08 20:43:28 UTC
This patch (also available for Apache 2.0 at
http://primero.ricilake.net/proxy2.patch ) implements a single directive:

ProxyAuthOverride 403 | 404 | Off

which, if not set to Off, converts 401 Unauthorized returns from a proxied
origin server into 403 or 404 status codes. It is intended for use in a reverse
proxy environment where it is not desirable to allow authentication with the
origin server.

Possibly the directive should also scrub Authorization: headers from the
request, as it is hard to imagine a use case where this is not desirable.
However, that can easily be done with mod_headers.
Comment 1 Rici Lake 2005-04-08 20:45:52 UTC
Created attachment 14666 [details]
Patch for mod_proxy.c to implement ProxyAuthOverride
Comment 2 William A. Rowe Jr. 2018-11-07 21:08:51 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.