httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gulati, Sushant" <>
Subject RE: [users@httpd] Wildcard SSL Certificate Traffic Segregation
Date Fri, 17 Jun 2011 14:04:15 GMT
Thanks a lot for your help Tom. I will try it out at my end.

Sushant Gulati

-----Original Message-----
From: Tom Evans [] 
Sent: Friday, June 17, 2011 7:29 PM
Subject: Re: [users@httpd] Wildcard SSL Certificate Traffic Segregation

On Fri, Jun 17, 2011 at 2:51 PM, Gulati, Sushant
<> wrote:
> First of all I really appreciate all the help I’ve received from this
> mailing list.
> We have a setup with a Wildcard SSL certificate for * There is
> a Tomcat server running in the background integrated with Apache through
> mod_jk. Till now, all the requests to were redirected to
> . Similarly all requests to
> were redirected to .
> Now we have a new requirement to have all requests to to be
> redirected to Tomcat A with the context root as mycontext and any other
> request, e.g. or to be redirected to
> Tomcat B with mycontext as the context root. The Name based Virtual Hosting
> will not work probably because of the SSL traffic. I am also thinking of
> using different context roots for different URLs, to segregate the traffic.
> Any help/suggestions/pointers would be most welcome J.

Name based vhosts work well with SSL as long as you are serving all
vhosts using the same certificate. If this is a wildcard certificate,
and all the domains used in the vhosts are covered by that
certificate, then name based vhosts will work fine.



The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:


This E-mail message and its attachments, if any are intended solely for the use of the addressee
hereof. In addition, this message and the attachments, if any may contain information that
is confidential, privileged and exempt from disclosure under applicable law. If you are not
the intended recipient of this message, you are prohibited from reading, disclosing, reproducing,
distributing, disseminating or otherwise using this transmission. 

Delivery of this message to any person other than the intended recipient is not intended to
waive any right or privilege. If you have received this message in error, please promptly
notify the sender by reply E-mail and immediately delete this message from your system.  Instructions
transmitted over this system are not binding on us until they are confirmed by us. Message
transmission is not guaranteed to be secure or free of software virus. While Altisource Portfolio
Solutions and its subsidiaries collectively "Altisource" takes every reasonable precaution
to minimize such risks, Altisource cannot accept liability for any damage sustained by you
or any third party as a result of software viruses.


View raw message