IISAPI and multiple IIS, Tomcat sites

[Jonathan Pierce <Jo...@seagram.com>]

I am running multiple servlets on my site, in seperate copies of Tomcat mapped
by the IISAPI filter with IIS.  I need to configure the machine so that some
sites are secure, and others are not.

I currently have two IIS sites that map requests to Tomcat, one that allows SSL
https secure connections only, and the other that allows unsecure http
connections.Both sites are configured to use the IISAPI filter to route
different requests to different copies of Tomcat listening on different APJ12 
ports.

I need to prevent unsecure connections to the servlets running in my intended
secure copy of Tomcat. The problem is, the IISAPI filter can only be configured
with a single workers.properties file since it's registry reference is
hard-coded. I'd like to be able to install two different IISAPI filter dll
copies, on different IIS sites, without sharing the same workers.properties conf
file so that I can configure access to different servlets from different sites.

Is there any way to do this without recompiling the IISAPI filter to look in a
different place in the registry for a different workers.properties file?

Jonathan Pierce

Re: IISAPI and multiple IIS, Tomcat sites

[Gal Shachor <sh...@il.ibm.com>]

Jonathan,
> 
> I am running multiple servlets on my site, in seperate copies of Tomcat mapped
> by the IISAPI filter with IIS.  I need to configure the machine so that some
> sites are secure, and others are not.
> 

Currently the plugins  (all of them) rely on the native web server for
per virtual
host/site configuration.

Unfortunately, IIS lack such support (for filters/extensions at least)
so we do not
have that implemented yet.

If you want to implement that yourself I can share my ideas with you
(lack of
time and other Tomcat issues prevents me from fixing that).

>
> I need to prevent unsecure connections to the servlets running in my intended
> secure copy of Tomcat. The problem is, the IISAPI filter can only be configured
> with a single workers.properties file since it's registry reference is
> hard-coded. I'd like to be able to install two different IISAPI filter dll
> copies, on different IIS sites, without sharing the same workers.properties conf
> file so that I can configure access to different servlets from different sites.
> 
> Is there any way to do this without recompiling the IISAPI filter to look in a
> different place in the registry for a different workers.properties file?
> 
What you really need is two worker mount files and you should mount each
site to the
wanted worker. IIS4 and above hand you over (in the request) an
identifier for the 
current site in use (generally something that looks like W3SVC1, W3SVC2
etc.). You
should be able to assign a worker map file per such ID and select the
correct map
for each request, and from there you should be able to select the
correct worker.

	Gal Shachor