If you have a site called "Site1" setup on the server under c:\site1 folder and you want to use UrlScan v3.1 as a site filter for this site, here is how you would set it up. There would be two instances of the filter running in this case. Upon installation of UrlScan v3.1 as a site filter requests for that particular site will run through both the site and the global filter if the global filter is not un-mapped. Check out the "Common Scenarios" section for some common configurations. Read through it and update the values for them according to your needs. The default UrlScan.ini file has detailed descriptions of what all the configuration options do. For IIS 6.0 make sure you give IIS_WPG write permissions to this folder, and for IIS 7.0 and above make sure you give IIS_IUSRS write permission to this folder. Make sure that IIS worker processes have write permissions to this folder. Change this to point to wherever you want your log files to be located. The default logging directory is the "logs" directory underneath the "UrlScan" directory where your global filter is installed. If you want to check out the new defaults for the UrlScan.ini file, download the new UrlScan.ini file here. If you are upgrading from UrlScan v2.5 or from UrlScan v3.0 your old UrlScan.ini file will be persisted and all your old settings will apply. See the Site Filter section on how to setup your filter as a site filter The default installation of UrlScan v3.1 installs the filter as a global filter. If you install UrlScan.dll filter from c:\foo and your IIS worker process loads the filter from this location, the configuration that will be applied to that instance of UrlScan is loaded from c:\foo\UrlScan.ini. In every case, the filter will read the UrlScan.ini configuration file from the same location that it loads UrlScan.dll. UrlScan v3.1 supports using the filter as both a global and site filter in conjunction, with the goal of having global rules in the global filter and application specific rules in the site filter. A site level filter is invoked only for requests to a particular site on the IIS server. A global filter is invoked for every HTTP request to the IIS server on which it is set up. UrlScan v3.1 can be set up as either a global filter or site level filter. The MSI installer will do so for the global filter case, but if you are installing UrlScan as a site filter you will need to set UrlScan as the highest order filter. UrlScan is required to be the highest priority filter for it to function properly.Please refer to the Setting Up UrlScan v3.1 section for details. The default installation will install UrlScan as a global filter only.Upgrading from UrlScan v2.5 or UrlScan v3.0 will leave your old UrlScan.ini file intact.In the 圆4 case, only the system32 directory will have the UrlScan.ini file since the filter will turn off redirection when attempting to access UrlScan.ini, so both versions of the filter will access the same configuration under system32 directory Folder above will also contain the configuration file, UrlScan.ini.On successful installation you should have a "UrlScan" folder with UrlScan.dll under %windir%\system32\inetsrv and additionally under %windir%\syswow64\inetsrv as well for 圆4 installations.Run UrlScan v3.1 MSI installer for either x86 or 圆4 version depending on your platform.IIS version 5.1, 6.0 or 7.0 or above (depending on the platform).Windows XP, Windows Server 2003, Windows Vista or Windows Server 2008.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |