Page History
...
- To verify that browser-side and server-side data is properly correlated, specify the name of the session cookie that is used by the application in the settings.xml file. Session cookie names can be JSESSIONID, _sn, SID, etc. Contact your application administrator to find the name of the cookie.
To add the session cookie name
In the “Registry Path” field in the Registry Editor (AdminPoint > Settings > Registry Editor), enter the following path and click Go: registry/instances/www/<server_name>/<instance_name>/settings.
In the Xml Editor tab, search for the <filter-session-cookie> tag.
Add the applicable cookie name between the tag, for example:
<filter-session-cookie>_sn</filter-session-cookie>
Click Save.
NOTE The cookie session name for J2EE (JSESSIONID) is the default value for the <filter-session-cookie> tag.
Adding post-parameters collection for IIS6
To add post-parameters collection for IIS, see the following sections:
Inserting wildcard mapping for Precise post-parameters collection extension
Add the Precise post-parameters collection extension to the trusted list
Updating the collect-post-parameters tag
Inserting wildcard mapping for Precise post-parameters collection extension
By inserting wildcard application mapping, you can instruct IIS to allow ISAPI applications known as interceptors to intercept and examine every request before the requested page is sent to its mapped application. The effect is an application mapping that handles every file name extension.
NOTE You must be a member of the Administrators group on the local computer to perform the following procedure or procedures. As a security best practice, log in to your computer by using an account that is not in the Administrators group, and then use the runas command to run IIS Manager as an administrator. At a command prompt, type run as /User:Administrative_AccountName"mmc systemroot\system32\inetsrv\iis.msc".
To add a wildcard application mapping to a Web server or Web site
In IIS Manager, expand the local computer, expand the Web Sites folder, expand the "Default-Web-Site", right-click the virtual directory that you want to collect post parameters on, and then click Properties.
Click Add Wildcard Script Map.
In the Executable box, enter the full path or browse to the native handler (.dll or .exe file) that processes the request: <precise_root>\products\www\instances\<instance_id>\bin\IISFilter.dll
In the Name box, enter a name for the handler mapping.
Click OK.
Click Yes, to add the extension with an Allowed entry to the ISAPI and CGI Restrictions list. Repeat this for each virtual directory you want to collect post parameters in.
Add the Precise post-parameters collection extension to the trusted list
In IIS Manager, expand the local computer; expand the Web Services Extensions, Click Add a new Web service extension.
Put "Precise post parameters" as extension name.
Click Add. In the "Path to file" field type the path to the DLL:
<precise_root>\products\www\instances\<instance_id>\bin\IISFilter.dll
Click OK.
Mark the “Set extension status to Allowed” check box.
Click OK.
Updating the collect-post-parameters tag
To update the collect-post-parameters tag
In the “Registry Path” field in the Registry Editor (AdminPoint > Settings > Registry Editor), enter the following path and click Go: registry/instances/www/<server_name>/<instance_name>/settings.
In the Xml Editor tab, change the value of the <collect-post-parameters> tag to “true”.
Click Save.
Adding post-parameters collection for IIS7
To add post-parameters collection for IIS, see the following sections:
Inserting wildcard mapping for Precise post-parameters collection extension
Updating the collect-post-parameters tag
Inserting wildcard mapping for Precise post-parameters collection extension
By inserting wildcard application mapping, you can instruct IIS to allow ISAPI applications known as interceptors to intercept and examine every request before the requested page is sent to its mapped application. The effect is an application mapping that handles every file name extension.
NOTE You must be a member of the Administrators group on the local computer to perform the following procedure or procedures. As a security best practice, log in to your computer by using an account that is not in the Administrators group, and then use the runas command to run IIS Manager as an administrator. At a command prompt, type run as /User:Administrative_AccountName"mmc systemroot\system32\inetsrv\iis.msc".
NOTE It is highly recommended to install the Microsoft hotfix mentioned in KB 2505146 (http://support.microsoft.com/kb/2505146) as this solves a Microsoft IIS7 issue. Should you not apply the hotfix and continue to perform the following steps, your application will stop working.
To add wildcard application mapping to a Web server or Web site
Go to the Precise_root directory and run the following script:
products\www\install\psww_insert_isapi_handlers.bat <precise_root>
<instance_id> <site_name> add-handler PreciseWebHandler <filter_path>
where:
filter_pathThe path to the instance bin folder concatenated with "IISFilter", without the _32.dll or _64.dll extension.
For example: c:\precise\products\www\instances\2643\bin\IISFilter
For example:
products\www\install\psww_insert_isapi_handlers.bat "E:\Precise Installation" 2442 Petshop add-handler PreciseWebHandler "E:\Precise Installation\products\www\instances\2442\bin\IISFilter"
Updating the collect-post-parameters tag
To update the collect-post-parameters tag
In the “Registry Path” field in the Registry Editor (AdminPoint > Settings > Registry Editor), enter the following path and click Go:
registry/instances/www/<server_name>/<instance_name>/settings/server-side.
In the Xml Editor tab, change the value of the <collect-post-parameters> tag to “true”.
Click Save.
Adding post-parameters collection for all other supported Web servers
To add post-parameters collection for all other supported Web servers, see the following section:
NOTE This feature is not supported for Apache 1.3.
Updating the collect-post-parameters tag
...
To update the collect-post-parameters tag
In the “Registry Path” field in the Registry Editor (AdminPoint > Settings > Registry Editor), enter the following path and click Go:
registry/instances/www/<server_name>/<instance_name>/settings/server-side.
In the Xml Editor tab, change the value of the <collect-post-parameters> tag to “true”.
Click Save.
Removing post-parameters collection for IIS7
To remove wildcard application mapping from a Web server or Web site
Go to the Precise_root directory and run the following script:
products\www\install\psww_insert_isapi_handlers.bat <precise_root>
<instance_id> <site_name> remove-handler PreciseWebHandler <filter_path>
where:
filter_path The path to the instance bin folder concatenated with "IISFilter", without the _32.dll or _64.dll extension.
For example: c:\precise\products\www\instances\2643\bin\IISFilter
For example:
products\www\install\psww_insert_isapi_handlers.bat "E:\Precise Installation"
2442 Petshop remove-handler PreciseWebHandler "E:\Precise
Installation\products\www\instances\2442\bin\IISFilter"