Hello,
- Make sure CGI/ISAPI is enabled on the web server
I assume you are using
Windows Features for this.
- Enable ISAPI/CGI in the "Module mapping" of the web site
In the
Custom Properties tab of the
Web Site you can add a
custom property, something like that:
- Section field: system.webServer/handlers
- Name:accessPolicy
- Value: Read, Execute, Script
Add an entry in the server's "ISAPI restrictions" for the application executable file or libraries and enable it.
In the
ISAPI Filters tab of your web site you can configure the
ISAPI filter and its corresponding restriction.
- Add an entry in the server's "CGI restrictions" for the application executable file or libraries and enable it.
In order to add the CGI restriction, you can go in the
Custom Actions page and add the predefined
Launch file custom action with sequence.
Edit its properties like that:
- File to Launch field: [SystemFolder]inetsrv\appcmd.exe
Command Line field: set config -section:system.webServer/security/isapiCgiRestriction /+"[\[]path='[PathToYourCGI_Script]l',description=' TestRule',allowed='True'[\]]"
Make sure you set this custom action as a
deferred one and it is only executed during
Install Execution Stage Condition. Also, you need to uncheck the
Fail installation if custom action returns an error Execution Option because it the related CGI restriction is already defined, the custom action will fail.
Please let us know if that helped.
Best regards,
Dan
FOLLOW US
Get the latest news in Application Packaging