Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 37839 invoked from network); 11 May 2007 21:39:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 May 2007 21:39:40 -0000 Received: (qmail 1277 invoked by uid 500); 11 May 2007 21:39:43 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 1071 invoked by uid 500); 11 May 2007 21:39:42 -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: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 1060 invoked by uid 99); 11 May 2007 21:39:42 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 May 2007 14:39:42 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [80.229.52.226] (HELO grimnir.webthing.com) (80.229.52.226) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 May 2007 14:39:35 -0700 Received: from grimnir.webthing.com (localhost [127.0.0.1]) by grimnir.webthing.com (Postfix) with ESMTP id 78CBF2135 for ; Fri, 11 May 2007 22:39:12 +0100 (BST) Date: Fri, 11 May 2007 22:39:12 +0100 From: Nick Kew To: dev@httpd.apache.org Subject: Re: ProxyPass globbing Message-ID: <20070511223912.21528c54@grimnir> In-Reply-To: References: Organization: WebThing X-Mailer: Sylpheed-Claws 2.5.0-rc3 (GTK+ 2.10.6; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Fri, 11 May 2007 15:19:58 -0400 Jim Jagielski wrote: > I've been looking at extending ProxyPass to > accept and use globbing patterns (basically, > to make it easier for those migrating from > mod_jk and JkMount to Apache 2.2), and it's > almost trivially easy, but there are some > "gotchas": Two half-thoughts: Is there a strong reason to prefer globs over regexps? A regexp doesn't have to be more complex than a glob, but gives the user who wants it that bit more hack-fu, and enables things people will want like ProxyPass \.(gif|jpe?g|png)$ http://backend/ Second, putting ProxyPass in a Directory context accomplishes the same thing more simply by enabling on it. > 1. ProxyPass /foo/* balancer://bar > should silently rewrite itself to > ProxyPass /foo/ balancer://bar > > In other words, we already assume a prefix > glob. But should we? In other words, > there is no difference between /foo/ and /foo/*. Yes. The currrent semantics of ProxyPass work well. We don't want to break them. > 2. ProxyPass /*.gif balancer://bar > How to handle /i/j/jim.gif? Should > the resultant proxy request be > balancer://bar/i/j/jim.gif (ie: the whole > glob) or balancer://bar/jim.gif. > I think the former is the most logical > and the most unsurprising. I agree in principle, but I'm a little uneasy about having inconsistency between that and globbing in and family. > Assuming that the interpretations of #1 and #2 > are semi-universal, any other comments? So, basically, > we are "just" adding suffix globbing to our already > existing prefix "globbing"... +0 (no strong views on it). +1 if you want to tackle wrowe's comments on my related patch at the same time, as I really don't know when I'll have any time for that. -- Nick Kew Application Development with Apache - the Apache Modules Book http://www.apachetutor.org/