Hi Mark,
I'm little confused about it.
Let assume my m/c ip is: 10.212.85.8
SSL connector are configured on ports: 8443 8553
I need to deploy one web app (myapp01.war) on port 8443 and another on
web app (myapp02.war) on 8553. Is there any way to configure to access
these web apps as:
https://10.212.85.8:8443/myapp01/
and
https://10.212.85.8:8553/myapp02/
Please find enclosed my conf file (i.e. server.xml) for reference.
Please let me know in case any other details are needed.
Thanks,
-Hitesh
-Original Message-
From: Mark Thomas [mailto:[EMAIL PROTECTED]
Sent: Monday, December 24, 2007 7:41 PM
To: Tomcat Users List
Subject: Re: multi-connector capability for HTTPS in Tomcat
Hitesh Raghav wrote:
Hi,
Does Tomcat support multi-connector capabilities for HTTPS?
Yes.
Edit The Tomcat Configuration File section in Tomcat's User-Guide
(http://tomcat.apache.org/tomcat-5.5-doc/ssl-howto.html
http://tomcat.apache.org/tomcat-5.5-doc/ssl-howto.html ) gives
impression that Tomcat could be configured using multiple connectors
to support HTTPS protocols on multiple ports simultaneously.
You can have multiple SSL connectors. Whilst connectors can listen on
multiple addresses, there can only be one connector listening on each
address/port combination.
Mark
-
To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe,
e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
?xml version=1.0 encoding=UTF-8?
!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the License); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an AS IS BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
--
!-- Example Server Configuration File --
!-- Note that component elements are nested corresponding to their
parent-child relationships with each other --
!-- A Server is a singleton element that represents the entire JVM,
which may contain one or more Service instances. The Server
listens for a shutdown command on the indicated port.
Note: A Server is not itself a Container, so you may not
define subcomponents such as Valves or Loggers at this level.
--
Server port=8005 shutdown=SHUTDOWN
!-- Comment these entries out to disable JMX MBeans support used for the
administration web application --
Listener className=org.apache.catalina.core.AprLifecycleListener /
Listener className=org.apache.catalina.mbeans.ServerLifecycleListener /
Listener className=org.apache.catalina.mbeans.GlobalResourcesLifecycleListener /
Listener className=org.apache.catalina.storeconfig.StoreConfigLifecycleListener/
!-- Global JNDI resources --
GlobalNamingResources
!-- Test entry for demonstration purposes --
Environment name=simpleValue type=java.lang.Integer value=30/
!-- Editable user database that can also be used by
UserDatabaseRealm to authenticate users --
Resource name=UserDatabase auth=Container
type=org.apache.catalina.UserDatabase
description=User database that can be updated and saved
factory=org.apache.catalina.users.MemoryUserDatabaseFactory
pathname=conf/tomcat-users.xml /
/GlobalNamingResources
!-- A Service is a collection of one or more Connectors that share
a single Container (and therefore the web applications visible
within that Container). Normally, that Container is an Engine,
but this is not required.
Note: A Service is not itself a Container, so you may not
define subcomponents such as Valves or Loggers at this level.
--
!-- Define the Tomcat Stand-Alone Service --
Service name=Catalina
!-- A Connector represents an endpoint by which requests are received
and responses are returned. Each Connector passes requests on to the
associated Container (normally an Engine) for processing.
By default, a non-SSL HTTP/1.1 Connector is established on port 8080.
You can also enable an SSL HTTP/1.1 Connector on port 8443 by
following the instructions below and uncommenting the second Connector
entry. SSL support requires the following steps (see the SSL Config
HOWTO in the Tomcat 5 documentation bundle for more detailed
instructions):
* If your JDK version 1.3 or prior, download
