From: "William A. Rowe, Jr."
>>
>> Doesn't the Apache on Windows web server have
>> available a built-in Windows Scripting Engine and two
>> built-in scripting languages, that do not use the # as
>> a scripting comment marker?
> No; Windows has a command-line Windows Scripting Host
> (cscript, a
At 09:11 AM 3/22/2003, Jeff White wrote:
>>> wrowe 2003/02/23 14:37:35
>>>
>>> Modified:modules/arch/win32 mod_win32.c
>>> Log:
>>> utf-8 win32 prefix when testing for shebang lines.
>
>Doesn't the Apache on Windows web server have
>available a built-in Windows Scripting Engine and
* 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
> (
>> wrowe 2003/02/23 14:37:35
>>
>> Modified:modules/arch/win32 mod_win32.c
>> Log:
>> utf-8 win32 prefix when testing for shebang lines.
Doesn't the Apache on Windows web server have
available a built-in Windows Scripting Engine and two
built-in scripting languages, that do not use
* William A. Rowe, Jr. wrote:
> Agreed. But I don't see this a radical change, it's actually very simple
> respect for folks authoring I18N scripts. I respect their effort, and would
> still like to backport this patch to help their efforts along.
Ok, convinced. We should support I18N in any wa
At 03:17 AM 3/19/2003, André Malo wrote:
>* [EMAIL PROTECTED] wrote:
>
>> wrowe 2003/02/23 14:37:35
>>
>> Modified:modules/arch/win32 mod_win32.c
>> Log:
>> Someone (I need to refer back) asked that we do the same skip for the
>> utf-8 win32 prefix when testing for shebang li
* [EMAIL PROTECTED] wrote:
> wrowe 2003/02/23 14:37:35
>
> Modified:modules/arch/win32 mod_win32.c
> Log:
> Someone (I need to refer back) asked that we do the same skip for the
> utf-8 win32 prefix when testing for shebang lines. Here's just such
> a test with some bad
