From: Chuck Murcko <chuck@n2k.com>
Message-Id: <199612120255.VAA16745@spudboy.telebase.com>
Subject: Restricting access to Proxy (fwd)
To: shuman@triton.kaifnet.com
Date: Wed, 11 Dec 1996 21:55:00 -0500 (EST)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@hyperreal.com

Hi. You can do this with Directory blocks and Limit directives:

<Directory proxy:*>
...
</Directory>

> ----- Forwarded message from M Shariful Anam -----
> 
> Message-Id: <32AE9349.5B80@triton.kaifnet.com>
> Date: Wed, 11 Dec 1996 04:56:09 -0600
> From: M Shariful Anam <shuman@triton.kaifnet.com>
> Organization: Kaifnet Services (Bangladesh)
> X-Mailer: Mozilla 3.0Gold (Win95; I)
> Mime-Version: 1.0
> To: apache-bugs@apache.org
> Subject: Restricting access to Proxy
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
> 
> Hi,
> 
> Is there any way such that I can restrict the access to the proxy
> feature of apache from certain host(s), but they will still be able to
> access the server? If not, I think you should add a filter_module in the
> future releases.
> 
> Thanks.
> 
> ----- End of forwarded message from M Shariful Anam -----

chuck
Chuck Murcko	N2K Inc.	Wayne PA	chuck@telebase.com
And now, on a lighter note:
"You've got to have a gimmick if your band sucks."
		-- Gary Giddens