If you are using only SSL without client (smarotcard etc) authentication, you could to it so: <VirtualHost SSL_IP:SSL_PORT> ... ProxyPass / http://localhost/ ProxyPassReverse / http://localhost/ ... </VirtualHost> (also you should have mod_rpaf taken into use for correct IP-s. You would be doing double proxying, but could have named based thing working fine.) Another solution would be doing conditional rewriting in SSL host for hostname (http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html#rewritecond). Br, Margus On Fri, 2011-06-17 at 19:21 +0530, 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 *.mydomain.com. > There is a Tomcat server running in the background integrated with > Apache through mod_jk. Till now, all the requests to www.mydomain.com > were redirected to www.mydomain.com/mycontext/ . Similarly all > requests to abc.mydomain.com were redirected to > abc.mydomain.com/mycontext/ . > > > > Now we have a new requirement to have all requests to www.mydomain.com > to be redirected to Tomcat A with the context root as mycontext and > any other request, e.g. abc.mydomain.com or def.mydomain.com 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. > > > > Regards, > > Sushant Gulati > > _______________________________________________________________________________ > > > > > > > > > ******************************************************************************************************* > > > > 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. > > > > ******************************************************************************************************* > > > --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|