mod_proxy/3830: What are the equivalents to the CERN proxy server's Pass and Fail directives?

[Kai-Uwe Rommel <ro...@ars.de>]

>Number:         3830
>Category:       mod_proxy
>Synopsis:       What are the equivalents to the CERN proxy server's Pass and Fail directives?
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          support
>Submitter-Id:   apache
>Arrival-Date:   Thu Feb  4 04:40:01 PST 1999
>Last-Modified:
>Originator:     rommel@ars.de
>Organization:
apache
>Release:        1.3.4
>Environment:
Apache 1.3.4 on OS/2
>Description:
Apache 1.3.4 works quite well on OS/2 here as a proxy server. We have
used CERN derivates until now (Lotus Go and Domino) that provided the "Pass"
and "Fail" configuration directives. Using these, it was possible to configure
the proxy so that certain URL types (such as "ftp:*") or certain URL
patterns (such as "http:*.zip") could be blocked from being retrieved over
that proxy ("Fail ftp:*" and "Fail http:*.zip" and so on).

I cannot find a equivalent configuration directive for Apache. How is something
like that done? I would like to be able to block our proxy users from
downloading files over that proxy at least to some degree (bandwidth issues).
>How-To-Repeat:

>Fix:

>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]