Technical data

12 Installing and Configuring the Microsoft Internet Information Server (ISAPI) Plug-In
12-8 Administration Guide
l port is the port number where IIS listens for HTTP requests.
l dll_directory is the path to the directory you created in step 1.
For example:
vhost1=strawberry.com:7001
strawberry.com:7001=c:\strawberry\iisproxy.ini
vhost2=blueberry.com:7001
blueberry.com:7001=c:\blueberry\iisproxy.ini
...
5. Create a separate iisproxy.ini file for each virtual Website, as described in
step 8. in “Proxying Requests”. For each virtual Website, copy this
iispoxy.ini
file to the directory you created in step 1.
6. Copy
iisproxy.dll to each directory you created in step 1.
7. In IIS, set the value for the Application Protection option to high (isolated). If the
Application Protection option is set to Medium(pooled), the iisproxy.dll that
registered as the first website will always be invoked. In this event, all the
requests will be proxied to the same WLS instances defined in the iisproxy.ini of
the first website.
Creating ACLs through IIS
ACLs will not work through the Microsoft Internet Information Server Plug-In if the
Authorization header is not passed by IIS. Use the following information to ensure that
the Authorization header is passed by IIS.
When using Basic Authentication, the user is logged on with local log-on rights. To
enable the use of Basic Authentication, grant each user account the Log On Locally
user right on the IIS server. Note the following two problems that may result from
Basic Authentication's use of local logon.
n If the user does not have local log-on rights, Basic Authentication will not work
even if the FrontPage, IIS, and Windows NT configurations appear to be correct.
n A user who has local log-on rights and who can obtain physical access to the
host computer running IIS will be permitted to start an interactive session at the
console.