Nikola, Thank you very much for you good comments. I agree that port based servers are not common. The reason we use them is for separating for example internal web sites and external public web sites.
Using host name based virtual hosting, you have to give a different host name to each port. For example if you were serving http and https on the same host www.company.com, you now have to use secure.company.com for your port 443 and www.company.com for your port 80. I just wanted to see if there is a way to just use www.company.com and have Tomcat see the port too. Thanks again. Aria On Thu, 06 Oct 2005 15:33:15 +0200 you said: >Aria Bamdad wrote: > >>Hi, I asked this question yesterday and got no hints from anyone. >>Since then, I have been able to accomplish what I want using multiple >>instances of Tomcat. However, I would much rather use one instance >>and serve requests on different Apache port. >> >>Does anyone have ANY comments regarding my issue? >> >> > >Well, having different presentations by using different port numbers is >not a common practice these days, since Apache has Name-based VHosts. >Similarely, Tomcat supports Name-based VHosts only (unless I am greatly >mistaken). So, it would appear that your solution is the only applicable >one. > >The best choice is, of course, to go for name based VHosts, since it >integrates very well and makes your URLs look nice. BTW, 443 is HTTPS >port, which is different story. > >So, save yourself a lot of trouble and go for unified VHosts. One >observation, though - with multiple instances of TC you have greater >robustness. > >Nix. > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
