Received: by taz.hyperreal.com (8.8.3/V2.0) id LAA06017;
 Thu, 19 Dec 1996 11:02:15 -0800 (PST)
Received: from mail1.bellglobal.com by taz.hyperreal.com (8.8.3/V2.0) with
 ESMTP id LAA05996; Thu, 19 Dec 1996 11:02:09 -0800 (PST)
From: rasmus@mail1.bellglobal.com
Received: from inet-dev ([199.243.250.207]) by mail1.bellglobal.com
          (Netscape Mail Server v2.02) with SMTP id AAA3633
          for <new-httpd@hyperreal.com>; Thu, 19 Dec 1996 14:00:51 -0500
Date: Thu, 19 Dec 1996 14:02:49 -0500 (EST)
Reply-To: rasmus@mail1.bellglobal.com
Subject: Re: Trouble with Location/SetHandler
To: new-httpd@hyperreal.com
In-Reply-To: 
 <Pine.HPP.3.95.961219104134.28426A-100000@ace.nueva.pvt.k12.ca.us>
Message-ID: <ML-2.3.851022169.444.rasmus@inet-dev>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@hyperreal.com

> And so on. (although you could do <Location ~ "/+cgi-bin">). But I'm
> not sure the correct way to deal with this.
> 
> Anyone have any ideas?

Could we not simply always collapse leading slashes?  Obviously we
want the ability to have consecutive slashes within the string, but I
can't think of a situation where collapsing leading multiple slashes
would create a problem.  It is certainly something that needs to be
addressed quickly.

-Rasmus