Lighttpd

second that.

-- bobo12

second that.

-- bobo12

I achieved this using the following configuration. It seems to work although there may be other effects that I have missed as I have only tested it in my particular application:

$HTTPurl =~ "/cgi-bin/.*$" {
cgi-assign ( "" => "" )
}

This seems to work providing that the shell can determine how to execute the file (the script must contain a shbang line at the top).

-- Patrick Brennan

Thinking about my above comment a little more. In my case the files being executed a binaries. It is likely that (although I haven't checked) that lighttpd uses exec (or a variant) to execute cgi files. This means that the shell is not involved and my technique would only work with binary executables. Feel free to test this (I don't have time at the moment) and append a comment here for all to read.

-- Patrick Brennan

Further to the above, it seems to work for perl files as well. Maybe I'm missing something important (or maybe I've inadvertantly discovered a feature) but it seems to work for me.

-- Patrick Brennan

Just small caveat, lighttpd will attempt to execute any directories under the cgi-bin pattern match (if a user specifies them as a URL). This results in a 500 Server Error. I doesn't seem to have any other detrimental effects, so I am ignoring it for the time being.

-- Patrick Brennan

The following would work:

cgi-assign (
   "/cgi-bin/perl/" => "/usr/bin/perl",
   "/cgi-bin/python/" => "/usr/bin/python",
   "/cgi-bin/bash/" => "/bin/bash",
)

If you can seperate your scripts into different directories...

cgi.assign = ("/cgi-bin/" => "")

i was misleaded by u guys :)