Purpose and description of the filter
The main purpose of the filter is to give an alternative way of creating virtual hosts
under IIS. The filter can also work under Personal Web Server, giving the ability to have
more than one site. It identifies the different sites by their hostnames and maps all
requests, connected with the given site, to a physical location on the server. There are
two schemes of mapping (see below for detailed description of each scheme). Additionally
exceptions of the common way of mapping can be defined. These exceptions apply when
specific subdirectories are found in the requested URL. Exceptions can be defined globally
for all sites on a given IP as well as for a particular site.
Note: As the mapping exceptions can be global i.e. common for all sites on an IP and
personal for a specified site only we will name the global mapping exceptions ‘Common
mapping paths’ and the personal mapping exceptions – ‘Folder exceptions’.
To make things clear let’s take one simple example. Assume you are an ISP and you
host customer sites on your server. You have a /cgi-bin and a /img directories that you
want to be accessible for every customer because they should use some common scripts and
images. Of course every customer should have personal web root directory where to store
his files. Additionally some customers have more privileges and use /cgi-bin and /img
directories with different contents than the other users. And, in the end, all users
should see the shared directories in a same way.
If you use this filter you can manage this situation like this: Create a virtual host for
every user, assign him directory and mapping scheme. Define common mapping paths for the
two shared directories /cgi-bin and /img and direct them there, where are the files for
normal users. Only for the users with higher privileges you can define folder exceptions
for these two directories and direct them a different location or locations.
You can download help file for more information