By default all the scripts are mapped to the proper scripting engines and the plain HTML files are precessed by the Web server solely. Sometimes you may need to set your HTML pages to be parsed through some script engine before sending them to the Web server. This can be done by modifying the default script mapping in the Web server configuration.
Contact Technical Support with the request to configure custom mapping.
- To set HTML files to be processed by ASP engine:
- Connect to the server using IIS7 Remote Manager.
- In Features View, on the server, site, or applicationHome page, double-click Handler Mappings.
- If there is already a mapping for .html files, remove it.
- On the Handler Mappings page, in the Actions pane, click Add Script Map.
- In the Request path box, type a file name extension or a file name with extension.
- In the Executable box, type the full path or browse to the native handler that processes the request. You can copy the path to PHP engine from the *.asp mapping
- In the Name box, type a friendly name for the handler mapping.
- Click Request Restrictions.
- On the Mapping tab, select Invoke handler only if request is mapped to then select File.
- Press OK and then OK.
- To set HTML files to be processed by PHP engine:
- Perform the steps 1 - 3 from above.
- In the Actions pane, click Add Module Mapping...
- In the Add Module Mapping dialog box, specify the configuration settings as follows:
- Enter the file name extension in the Request path text box (*.html)
- Click FastCgiModule in the Module drop-down list.
- Enter the path to the scripting engine in the Executable box. (You can copy the path to PHP engine from the *.php mapping)
- Enter a unique name for the handler mapping in the Name box.
- Press OK.