Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
From: =?ISO-8859-1?Q?Andr=E9?= Malo <nd@perlig.de>
Subject: Re: cvs commit: httpd-2.0/modules/arch/win32 mod_win32.c
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Organization: TIMTOWTDI
References: <20030223223735.7916.qmail@icarus.apache.org>
 <5.2.0.9.2.20030319095124.0118fe68@pop3.rowe-clan.net>
 <000201c2f15d$da29a4d0$4481f6d1@RUFF01>
Date: Sun, 23 Mar 2003 20:26:16 +0100
To: dev@httpd.apache.org
Message-ID: <n2m-g.10r7afed5jgig$ndparker@news.perlig.de>
User-Agent: Yes!

* Jeff White wrote:

> Usage with the built-in Windows Scripting Engine by
> some Apache on Windows web servers, using the
> built-in scripting languages, is now doable via tricking
> the Apache on Windows web server. Tricking the server
> with a fake file, that uses the "pain" Unix based # way
> (or with an option that also turns on everything else at
> the same time) - ScriptInterpreterSource.

You may want to try ScriptInterpreterSource registry-strict.
This uses the ExecCGI\Command key instead of Open\Command.

> But isn't it
> possible to also check for // (two slashes for JScript
> usage) or for a ' (a single quote for VBScript usage)
> during the Apache on Windows script usage routine?

#! is not a real comment (just to be clear). However, the windows way to=20
recognize the interpreter is "query the registry". That's what=20
ScriptInterpreterSource is intended for. I cannot see any reason to=20
recognize other chars than (BOM)#! at the start of the script (which is=20
done _only_ for some unix-compat reasons).

nd
--=20
"Die Untergeschosse der Sempergalerie bleiben w=E4hrenddessen aus
 statistischen Gr=FCnden geflutet." -- Spiegel Online