Le 2012-07-18 10:39, clipka a écrit :
> Am 18.07.2012 16:28, schrieb Francois Labreque:
>> Le 2012-07-17 10:34, Invisible a écrit :
>>> Typically the host sets up a special folder, and any files within it are
>>> considered to be CGI scripts in whatever language the server is
>>> hard-coded to accept. (Or /maybe/ based on the filename.) Presumably
>>> you'd have to find a host that allows executable binaries...
>>
>> On Apache, it _is_ done by filename.  Since the host has to "chmod" the
>> files to make them executable (on *NIX), it probably automagically does
>> this on a specific set of file extensions.  so you need to find out what
>> extensions are supported.
>
> Comes as a surprise to me, given that it's Unix customary practice to
> identify file types by signatures.

I meant to say that a web hosting service might have some automated 
process that would automatically chmod +x any file with the .pl or .cgi 
extension that the user uploads to his or her cgi-bin/ directory, 
whereas a .jpg or .html wouldn't be chmodded.

And you are right, Unices do use file signatures to determine what to do 
with them, that's why I told Andy that if he uploaded a compiled Haskell 
binary and simply named it "andy.pl" it might run anyway as the web 
server would more than likely issue a system() call and let the OS 
figure out what to do with it.

-- 
/*Francois Labreque*/#local a=x+y;#local b=x+a;#local c=a+b;#macro P(F//
/*    flabreque    */L)polygon{5,F,F+z,L+z,L,F pigment{rgb 9}}#end union
/*        @        */{P(0,a)P(a,b)P(b,c)P(2*a,2*b)P(2*b,b+c)P(b+c,<2,3>)
/*   gmail.com     */}camera{orthographic location<6,1.25,-6>look_at a }

Post a reply to this message