ApacheWS 2.4-58 on VMS 9.2-2

[arne_v]

I am having a small problem.

Static HTML : fine
PHP : fine
CGI COM : fine
CGI EXE : fails

My test example is this.

nop.c -> nop.exe:

Code: Select all

#include <stdio.h>
#include <stdlib.h>
#include <string.h>

int main()
{
    printf("content-type: text/plain\r\n");
    printf("\r\n");
    printf("OK\r\n");
    return 0;
}

runnop.com:

Code: Select all

$ run nop
$ exit

/cgi-bin/runnop works fine but /cgi-bin/nop fails.

access_log:

192.168.68.89 - - [17/Mar/2024:14:32:50 -0500] "GET /cgi-bin/runnop HTTP/1.1" 200 4
192.168.68.89 - - [17/Mar/2024:14:33:02 -0500] "GET /cgi-bin/nop HTTP/1.1" 500 620

but the big mystery is in error_log:

[Sun Mar 17 14:33:03.087209 2024] [cgi:error] [pid 1054] [client 192.168.68.89:51333] malformed header from script 'nop.EXE': Bad header: %DCL-W-IVVERB, unrecognized co
[Sun Mar 17 14:33:03.097209 2024] [cgi:error] [pid 1054] [client 192.168.68.89:51333] AH01215: : /apache$root/cgi-bin/nop.EXE
[Sun Mar 17 14:33:03.107208 2024] [cgi:error] [pid 1054] [client 192.168.68.89:51333] AH01215: %DCL-W-IVVERB, unrecognized command verb - check validity and spelling\r: /apache$root/cgi-bin/nop.EXE
[Sun Mar 17 14:33:03.107208 2024] [cgi:error] [pid 1054] [client 192.168.68.89:51333] AH01215: \\\x7fELF\x02\x01\x01\r\x02\\\r: /apache$root/cgi-bin/nop.EXE
[Sun Mar 17 14:33:03.117208 2024] [cgi:error] [pid 1054] [client 192.168.68.89:51333] AH01215: %DCL-W-UNDSYM, undefined symbol - check validity and spelling\r: /apache$root/cgi-bin/nop.EXE
[Sun Mar 17 14:33:03.117208 2024] [cgi:error] [pid 1054] [client 192.168.68.89:51333] AH01215: \\�?\\\r: /apache$root/cgi-bin/nop.EXE
[Sun Mar 17 14:33:03.117208 2024] [cgi:error] [pid 1054] [client 192.168.68.89:51333] AH01215: %DCL-W-IVVERB, unrecognized command verb - check validity and spelling\r: /apache$root/cgi-bin/nop.EXE
[Sun Mar 17 14:33:03.117208 2024] [cgi:error] [pid 1054] [client 192.168.68.89:51333] AH01215: \\\x14\\\r: /apache$root/cgi-bin/nop.EXE
[Sun Mar 17 14:33:03.127208 2024] [cgi:error] [pid 1054] [client 192.168.68.89:51333] AH01215: %DCL-W-IVVERB, unrecognized command verb - check validity and spelling\r: /apache$root/cgi-bin/nop.EXE
[Sun Mar 17 14:33:03.127208 2024] [cgi:error] [pid 1054] [client 192.168.68.89:51333] AH01215: \\\x10\\\r: /apache$root/cgi-bin/nop.EXE
[Sun Mar 17 14:33:03.127208 2024] [cgi:error] [pid 1054] [client 192.168.68.89:51333] AH01215: %DCL-W-IVVERB, unrecognized command verb - check validity and spelling\r: /apache$root/cgi-bin/nop.EXE
[Sun Mar 17 14:33:03.127208 2024] [cgi:error] [pid 1054] [client 192.168.68.89:51333] AH01215: \\0\\\r: /apache$root/cgi-bin/nop.EXE
[Sun Mar 17 14:33:03.127208 2024] [cgi:error] [pid 1054] [client 192.168.68.89:51333] AH01215: %DCL-W-IVVERB, unrecognized command verb - check validity and spelling\r: /apache$root/cgi-bin/nop.EXE
[Sun Mar 17 14:33:03.127208 2024] [cgi:error] [pid 1054] [client 192.168.68.89:51333] AH01215: \\\x19\\\r: /apache$root/cgi-bin/nop.EXE
[Sun Mar 17 14:33:03.137208 2024] [cgi:error] [pid 1054] [client 192.168.68.89:51333] AH01215: %DCL-W-IVVERB, unrecognized command verb - check validity and spelling\r: /apache$root/cgi-bin/nop.EXE
[Sun Mar 17 14:33:03.137208 2024] [cgi:error] [pid 1054] [client 192.168.68.89:51333] AH01215: \\\x18\\\r: /apache$root/cgi-bin/nop.EXE
[Sun Mar 17 14:33:03.137208 2024] [cgi:error] [pid 1054] [client 192.168.68.89:51333] AH01215: %DCL-W-IVVERB, unrecognized command verb - check validity and spelling\r: /apache$root/cgi-bin/nop.EXE
[Sun Mar 17 14:33:03.137208 2024] [cgi:error] [pid 1054] [client 192.168.68.89:51333] AH01215: \\VSI\\\r: /apache$root/cgi-bin/nop.EXE
[Sun Mar 17 14:33:03.137208 2024] [cgi:error] [pid 1054] [client 192.168.68.89:51333] AH01215: %DCL-E-OPENIN, error opening \x0e\x10\x17\x1b\x0e\xb4B\x19\x11\x01\x12\x06 as input\r: /apache$root/cgi-bin/nop.EXE
[Sun Mar 17 14:33:03.137208 2024] [cgi:error] [pid 1054] [client 192.168.68.89:51333] AH01215: -RMS-F-SYN, file specification syntax error\r: /apache$root/cgi-bin/nop.EXE

What is happening?

And how can I fix it?

[craigberry]

Dunno, but in case you haven't checked the obvious, does:

$ mcr apache$root:[cgi-bin]nop.EXE

work?

[arne_v]

Dunno, but in case you haven't checked the obvious, does:

$ mcr apache$root:[cgi-bin]nop.EXE

work?

Yes.

And the runnop.com above also works fine as CGI script.

But I can't get nop.exe to run without the wrapper.

And I think the error message is weird.

It is almost like Apache is trying to @ the EXE.

Also worth noting is that an old CSWS on VMS Alpha has no problems with EXE.

[sms]

Code: Select all

> Also worth noting is that an old CSWS on VMS Alpha has no problems
> with EXE.

   I did a similar program/script thing on my main IA64 system
(V8.4-2L3) a while ago (22-DEC-2021) with no trouble.  (Still at "VSI
I64VMS CSWS V2.4-54" there.)  It still works there, and it fails the
same way for me on V9.2-2 with "VSI X86VMS APACHEWS V2.4-58".

> What is happening?
> 
> And how can I fix it?

   I know nothing, but I wouldn't be amazed by a bug in either "X86VMS
APACHEWS" or, say, system() on x86_64.  (My memory's useless, but wasn't
there some kind of bug someplace involving recognizing executables as
executables on x86_64?  False memory syndrome?)

   Someone should try this on Alpha or IA64 with "VSI X86VMS APACHEWS
V2.4-58".  I'm a little afraid to disturb my main web server right now.

[arne_v]

> Also worth noting is that an old CSWS on VMS Alpha has no problems
> with EXE.

I did a similar program/script thing on my main IA64 system
(V8.4-2L3) a while ago (22-DEC-2021) with no trouble. (Still at "VSI
I64VMS CSWS V2.4-54" there.) It still works there, and it fails the
same way for me on V9.2-2 with "VSI X86VMS APACHEWS V2.4-58".

> What is happening?
>
> And how can I fix it?

I know nothing, but I wouldn't be amazed by a bug in either "X86VMS
APACHEWS" or, say, system() on x86_64.

...

Someone should try this on Alpha or IA64 with "VSI X86VMS APACHEWS
V2.4-58". I'm a little afraid to disturb my main web server right now.

OK, so the problem is reproducable on other systems.

And running CGI EXE without COM wrapper is a pretty basic feature.

I think VSI should fix.