Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 99695 invoked by uid 500); 18 Jan 2002 14:41:43 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 99681 invoked from network); 18 Jan 2002 14:41:43 -0000 Message-ID: <3C483426.6050400@apache.org> Date: Fri, 18 Jan 2002 06:41:42 -0800 From: Ian Holsman User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.7+) Gecko/20020115 X-Accept-Language: en-us MIME-Version: 1.0 To: Jim Jagielski , dev@httpd.apache.org Subject: Re: [PROPOSAL] New regex Proxy directives References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Jim Jagielski wrote: > The current usage of mod_proxy in forward proxy scenarios is limited > by the limited "pattern" matching capabilities of NoProxy and > ProxyRemote. I am working on a patch that adds NoProxyMatch and > ProxyRemoteMatch which makes them regex aware. are you going to do something similiar with proxypass/proxypassreverse? If it would be possible to have 2 lists... a nonregex and a regex list when you do the actual match against the URL that would be great. ..Ian > > Just a head's up. > > PS: This will be for 2.0 only, but may backport to 1.3.x as well. >