Bug 40746 - Feature request: ProxyAllow directive
Summary: Feature request: ProxyAllow directive
Status: RESOLVED LATER
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_proxy (show other bugs)
Version: 2.0.58
Hardware: Other Linux
: P3 enhancement (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: MassUpdate
Depends on:
Blocks:
 
Reported: 2006-10-12 11:50 UTC by Trevin Beattie
Modified: 2018-11-07 21:08 UTC (History)
0 users



Attachments
patch to create a new ProxyAllow directive in mod_proxy (14.19 KB, patch)
2006-10-12 11:52 UTC, Trevin Beattie
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Trevin Beattie 2006-10-12 11:50:42 UTC
My company has an Apache proxy server which is used not as a firewall, but as a
whitelisted passthrough.  So we need to be able to restrict incoming requests to
just a selected set of servers.

One of the services we will be proxying to requires the use of an HTTP CONNECT
instead of the usual RewriteRule we use to select most of the other services. 
But the AllowCONNECT directive in the stock Apache distribution doesn't provide
any way to restrict connections to certain hosts; it only restricts what ports
can be connected to.

The ProxyBlock directive is the closest analogue to what we need.  It blocks
given hosts, but allows all others.  We need just the opposite: to allow given
hosts, but block all others.

So I created the following patch (against 2.0.59) which basically just uses the
same code as ProxyBlock but reverses its meaning.

If a ProxyAllow directive exists in the configuration, then all proxy targets
will be blocked except for those listed.  If this directive is not present, then
Apache allows all target hosts by default.

There are of course further improvements that could be made, but which I didn't
have time to implement: a directive like Order that would specify whether to
evaluate ProxyAllow before or after ProxyBlock; and a way to specify whether the
ProxyBlock and ProxyAllow directives apply to only rewrite rules, AllowCONNECT,
or both.  (Currently these directives apply to all types of proxies.  We only
needed it for the AllowCONNECT directive.)
Comment 1 Trevin Beattie 2006-10-12 11:52:29 UTC
Created attachment 18996 [details]
patch to create a new ProxyAllow directive in mod_proxy
Comment 2 William A. Rowe Jr. 2018-11-07 21:08:55 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.