DO NOT REPLY [Bug 7786] - ScriptInterpreterSource is broken

2002-06-24 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7786

ScriptInterpreterSource is broken





--- Additional Comments From [EMAIL PROTECTED]  2002-06-24 09:34 ---
Supplement to last comment:
The error messages in the mod_ssl case are a little bit different:
[Mon Jun 24 11:31:18 2002] [error] [client 127.0.0.1] (22)Invalid argument:
couldn't create child process: 22: E:/Web/cgi-bin/test.cgi
[Mon Jun 24 11:31:18 2002] [error] [client 127.0.0.1] (22)Invalid argument:
couldn't spawn child process: E:/Web/cgi-bin/test.cgi

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 7786] - ScriptInterpreterSource is broken

2002-06-24 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7786

ScriptInterpreterSource is broken





--- Additional Comments From [EMAIL PROTECTED]  2002-06-24 08:38 ---
Combining the two lines didn't make any difference. Still Apache2 does not
recognize the ".cgi"-scripts.

But I found another difference.
Looking into the registry with regedt32, it showed, that the Perl installation
generated the entry for key "command" (under "Perl", "shell", "Open") with type
REG_SZ, but the NT-Explorer created the key "command" (under "cgifile", "shell",
"Open") with a value of type REG_EXPAND_SZ.
Deleting the value of this key with regedit (key "(Standard)" under "cgifile",
"shell", "Open", "command") and then entering a new value there (again the
invocation for the Perl installation: "D:\Programme\Perl\bin\perl.exe" "%1" %*)
generated a value of type REG_SZ. And now this entry works!!

By the way: I also tried the mod_ssl from
"Apache-2.0.39-Mod_SSL-OpenSSL-0.9.6d-Win32.zip" from
"http://www.modssl.org/contrib/";, and with https ".cgi"-scripts still didn't
work, while ".pl"-scripts are fine. The above procedure changed only the
behavior fot http-requests, not for https-requests (I have to rely on
"http://www.modssl.org/contrib/";, as I don't have a compiler environment on my
NT machine).

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 7786] - ScriptInterpreterSource is broken

2002-06-21 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7786

ScriptInterpreterSource is broken





--- Additional Comments From [EMAIL PROTECTED]  2002-06-21 17:33 ---
Just for fun, try combining the lines;

AddHandler cgi-script .cgi
AddHandler cgi-script .pl

into;

AddHandler cgi-script .cgi .pl

and see what happens.  I'm simply wondering if the .pl association didn't 
clobber
the .cgi association in that container.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 7786] - ScriptInterpreterSource is broken

2002-06-21 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7786

ScriptInterpreterSource is broken





--- Additional Comments From [EMAIL PROTECTED]  2002-06-21 16:52 ---
You were looking for other reports on this fault on Apache 2.0. Mine looks 
similar:
I have the following 1 line perl script:

print "Content-type: text/plain\n\nHello perl\n".localtime(time)."\n";

If the name of the script is "test.pl", the script is executed fine.
If the name is "test.cgi", I get the following log error lines:
[Fri Jun 21 18:10:09 2002] [error] [client 127.0.0.1] E:/Web/cgi-bin/test.cgi is
not executable; ensure interpreted scripts have "#!" first line
[Fri Jun 21 18:10:09 2002] [error] [client 127.0.0.1] (9)Bad file descriptor:
don't know how to spawn child process: E:/Web/cgi-bin/test.cgi
and the error message
  E:/Web/cgi-bin/test.cgi is not executable; ensure interpreted scripts have
"#!" first line
with Error 500 is sent to the browser.

The script is executed without error under both names on the same machine on
Apache 1.3.26. This means, that the registry is exactly the same for both Apache
installations.
Also invocation from command line works fine for both file names.

The only difference I know is, that the registry entry for ".pl" was done by the
Perl installation (currently ASPN 5.6.1 Build 633) and the entry for ".cgi" was
done manually in NT-Explorer with the same parameter for "Open" as copied from
".pl" ("D:\Programme\Perl\bin\perl.exe" "%1" %*) and no DDE enabled.

-
System: WinNT 4.0 SP6a, Apache installed from 
"apache_2.0.39-win32-x86-no_ssl.msi".

Snippet from httpd.conf (for both installations):
-
ScriptInterpreterSource registry

AllowOverride Limit
Options ExecCGI
AddHandler cgi-script .cgi
AddHandler cgi-script .pl
Order allow,deny
Allow from all

-

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 7786] - ScriptInterpreterSource is broken

2002-06-02 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7786

ScriptInterpreterSource is broken

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2002-06-02 16:13 ---

  This looks like a configuration bug rather than a continued
  bug with ScriptInterpreterSource.

  1. you are using a win32 build, not a cygwin build, correct?

  2. You remembered to associate your files with ScriptAlias
 or used Options ExecCGI and AddHandler cgi-script .cgi?

  You need to provide more info about HOW it is failing, including
  a snip from your error log file, please, before reopening this
  bug.  There have been no other reports for 2.0.36 of this fault.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 7786] - ScriptInterpreterSource is broken

2002-06-02 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7786

ScriptInterpreterSource is broken

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 OS/Version|Windows NT/2K   |Windows XP
   Priority|Other   |Medium
 Resolution|FIXED   |
Version|2.0.35  |2.0.36



--- Additional Comments From [EMAIL PROTECTED]  2002-06-02 11:52 ---
Still unresolved under Apache 2.0.36 :-(
(under Windows XP)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 7786] - ScriptInterpreterSource is broken

2002-04-17 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7786

ScriptInterpreterSource is broken





--- Additional Comments From [EMAIL PROTECTED]  2002-04-17 03:18 ---

Based on my observations, it's also possible to work around this bug while 
waiting
for Apache 2.0.36.

By removing or crippling the shebang line, the cgi parser will go on to attempt
the registry method.  This can be done by adding an extra # in the first line of
a script, such as;

##!perl

In this way, you have a reminder that there once was a shebang line, but it
won't be recognized because it doesn't begin with "#!"

And you can then use your registry associations to invoke the script instead.


DO NOT REPLY [Bug 7786] - ScriptInterpreterSource is broken

2002-04-17 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7786

ScriptInterpreterSource is broken

[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]



--- Additional Comments From [EMAIL PROTECTED]  2002-04-17 03:11 ---
*** Bug 8171 has been marked as a duplicate of this bug. ***


DO NOT REPLY [Bug 7786] - ScriptInterpreterSource is broken

2002-04-17 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7786

ScriptInterpreterSource is broken

[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]



--- Additional Comments From [EMAIL PROTECTED]  2002-04-17 03:10 ---
*** Bug 8182 has been marked as a duplicate of this bug. ***


DO NOT REPLY [Bug 7786] - ScriptInterpreterSource is broken

2002-04-12 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7786

ScriptInterpreterSource is broken

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED
Version|2.0.32  |2.0.35



--- Additional Comments From [EMAIL PROTECTED]  2002-04-12 06:40 ---

  It was not 'broken', e.g. no shebang line at all would cause the
  registry interpretation to run.

  However, it did attempt to use the shebang line over the registry
  if the shebang was present.  I believe this is a misordering, compared 
  to 1.3, and considering that the explicit preference is registry.

  This bug will be fixed in 2.0.36


DO NOT REPLY [Bug 7786] - ScriptInterpreterSource is broken

2002-04-06 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7786

ScriptInterpreterSource is broken





--- Additional Comments From [EMAIL PROTECTED]  2002-04-06 07:21 ---
oh yeah, the exact error is 

"(22502)The system cannot find the file specified.  : couldn't create child 
process: 22502"