David Wang [Msft] wrote:
> Then in Web Service Extensions you would have
> - Deny execute to all CGI except...
> - Allow C:\scripts\MyExe1.exe
> - Allow C:\scripts\MyExe2.exe
> - Allow C:\otherscripts\MyExe3.exe
The problem I see with this approach is that in my case the exe's are
individual per website. If there was a way, I would prefer to enable
all exe's (*.exe) but not allow all cgi's.
Or in IIS does CGI = exe (either directly or allowing scripts that are
filtered by an exe such as perl & php).
FYI, I don't use much perl except where it is left over from old sites,
and I don't use PHP. My exe's are exe's that I'm testing prior to
recompiling as DLL's.<!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: Web Service Extension for EXE's ?