At 12:35 PM -0800 2001/03/06, [EMAIL PROTECTED] wrote:
>If what you want to do is support virtual hosts - tomcat supports
>virtual hosts using a single ContextManager ( the contextManager is a
>representation for a "server" that may have multiple hosts).
>
>There is no special representation for Host ( as a top-level object ) -
>each Context belongs to a virtual host, and the mapper is routing the
>requests. You can add additional modules to filter or do other tricks.
>( just use Context.getHost() or getHostAliases() ).
Costin,
I see I can bind specific servlets to a host by name, but how
can I bind to a specific port? I want my webapp only available via
SSL, and a single homepage on port 80, redirecting users to port 443
to really use the site.
>There are cases when multiple ContextManagers may help - for example if
>the servers have very different configuration ( i.e. top-level modules
>for mapping, etc).
>
>In 3.3 ( with the experimental ProfileLoader ) you can push all the
>modules as per/context interceptors, i.e. separate sets of
>modules for each web application - what's shared is the config modules
>and the top-level mapper. That means even fewer reasons to have multiple
>ContextManagers.
I'm using 3.2.1 -- does 3.3 add the capability to bind
servlets/webapps to individual ports?
>IMHO if what you want to do requires changes/fixes in tomcat, you should
>try tomcat 3.3, where it is still possible to do this kind of change
>( assuming it's not too big ). For 3.2.2 I don't think this can be
>clasified as a critical bug, and I don't think Marc would enjoy it :-)
Thanks,
Chris Pepper
--
Chris Pepper: <http://www.reppep.com/~pepper/>
Rockefeller U Computing Services: <http://www.rockefeller.edu/>
Mac OS X Software: <http://www.mosxsw.com/>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
