[prev in list] [next in list] [prev in thread] [next in thread] 

List:       apache-modproxy-dev
Subject:    Re: Suggestions for mod_proxy
From:       Timothy Stone <citylists () petmystone ! com>
Date:       2003-08-07 12:26:49
[Download RAW message or body]

Timothy Stone wrote:

> Greetings mod_proxy developers:
> 
> Normally, I would not bother a developer list, but certain requirements 
> in a recent project sparked my desire to post a suggestion for mod_proxy.
> 
> The directive: ProxyBlock has very broad or very narrow application.
> 
> For example:
> 
> ProxyBlock *
> 
> Effectively disables Apache as a proxy.
> 
> Opposite is:
> 
> ProxyBlock .playboy.com .hustler.com .wired.com
> 
> which is a very grandular approach.
> 
> There is not an "in-between". Specifically, I was handed requirements to 
> set up a "kiosk-like" box that served local content, but could go to 
> Mapquest if desired. So my initial idea was to set Apache up as a proxy 
> that would block traffic to all websites /except/ Mapquest.
> 

I knew that I must have been missing a piece of the puzzle. Thanks to 
Andrew Braund for pointing me to the configuration guidelines for a 
"URL-Restricted Proxy" available in the Apache 1.3 URL Rewriting Guide 
(http://httpd.apache.org/docs/misc/rewriteguide.html).

Warmest Regards,
Tim


[prev in list] [next in list] [prev in thread] [next in thread]