httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 40746] New: - Feature request: ProxyAllow directive
Date Thu, 12 Oct 2006 18:50:42 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=40746>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40746

           Summary: Feature request: ProxyAllow directive
           Product: Apache httpd-2
           Version: 2.0.58
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P3
         Component: mod_proxy
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: tbeattie@boingo.com


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.)

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message