Received: by taz.hyperreal.com (8.8.3/V2.0) id NAA19911;
 Thu, 19 Dec 1996 13:35:55 -0800 (PST)
Received: from nora.pcug.co.uk by taz.hyperreal.com (8.8.3/V2.0) with SMTP id
 NAA19902; Thu, 19 Dec 1996 13:35:49 -0800 (PST)
Received: from imdb.demon.co.uk by nora.pcug.co.uk id aa29748;
          19 Dec 96 21:35 GMT
Message-Id: <199612192135.VAA03891>
Subject: Re: Trouble with Location/SetHandler
To: new-httpd@hyperreal.com
Date: Thu, 19 Dec 1996 21:35:40 +0000 (GMT)
In-Reply-To: <Pine.HPP.3.95.961219124649.1763A-100000@ace.nueva.pvt.k12.ca.us>
 from "Alexei Kosut" at Dec 19, 96 12:47:36 pm
From: Rob Hartill <robh@imdb.com>
Organization: Internet Movie Database Ltd.
X-pgp-public-key: http://us.imdb.com/pgp.html
X-Mailer: ELM [version 2.4 PL24 ME8a]
Content-Type: text
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@hyperreal.com

Alexei Kosut wrote:
>
>On Thu, 19 Dec 1996, Rob Hartill wrote:
>
>> Can Alias be made to trigger only from inside the <Location> ? 
>
>It doesn't matter - this problem has nothing to do with Alias.

No ?, then how does Apache know where the scripts to be printed are ?

The Alias maps the URL to a file, so if <Location > prevents or can
be made to prevent the mapping, then a ///foo request won't match
anything in the conf file. Only if <Location> is acted upon will
(in my theory/proposal) the Alias be expanded.

See what I mean ?

That way the CGI triggering <Location > would  use Alias to find the
directory of the URL, at which point <Location > has forced the
contents to be treated as CGI.

Basically, this 404 rejects URLs with //s in them unless they match the
<Location > argument.


rob