>What you generated was an .exe, no matter what you call it, >and if you want Apache to invoke perl and run it, you need >a perl script: > > <snip> > >if Apache is treating .cgi as if it is perl stuff. Apache >probably tried to get perl.exe to run the binary script.exp >and perl choked.
Interesting idea, but I'm not sure how it works logically. (the explanation, not the "you need a perl script" pp snippet).
Apache doesn't "treat .cgi as if it is perl stuff". It treats .cgi files with execute permissions as if they were executable files, which it spawns a second process to run them in. The necessity for the shebang is so the right interpreter is used for the job - Apache doesn't come into play as a determining factor at all (you can run .cgi scripts with Ruby, PHP, C, etc.).
There *are* times when the file extension determines the language to run them in, but that only happens under Windows (where a .pl is associated with the perl.exe binary) or in embedded languages (like PHP). Neither are applicable in this case (as he's under RedHat).
-- Morbus Iff ( i put the demon back in codemonkey ) Culture: http://www.disobey.com/ and http://www.gamegrene.com/ Spidering Hacks: http://amazon.com/exec/obidos/ASIN/0596005776/disobeycom icq: 2927491 / aim: akaMorbus / yahoo: morbus_iff / jabber.org: morbus
