|
I believe you'd need to set up virtual hosts in this case... and then for each ip:port specify the server name that it relates to. That means 2 listen directives.. one for each port... then virtual host directives and containers for each "site". Tomcat, if I remember, has config that is a "lite" version of Apache, so it should be possible. Brad www.bvstools.com On Fri, 1 Oct 2004 10:34:52 -0600 "Pete Helgren" <pete@xxxxxxxxxx> wrote: > This is more of a TCP/IP issue (I think) than iSeries web > server issue but > here is the question: > > I have a Tomcat server and a standard Apache server > running on our iSeries. > The default config has port 80 traffic on mycompany.com > going to the apache > server but I want myhost.mycompany.com traffic to map > back to port 9095 > where Tomcat is listening. So, I want to make a > distinction between port 80 > and port 9095 traffic by host name. I want > myhost.mycompany.com to go to > 10.0.0.101 on port 9095 while the mycompany.com traffic > to go to 10.0.0.100 > on port 80. How do I do that? Do I need to qualify the > host for the port 80 > traffic as well? (e.g. mydefaulthost.mycompany.com goes > to port 80 and > myhost.mycompany.com goes to port 9095) > > I have a quiet bell ringing in my head about how to do > this but I don't have > enough to get started. I know this is simple, just can't > quite remember the > rules. > > Any pointers? > > Pete Helgren > Timpanogos Technologies, Inc > 801.892.9106 x 202 > > > Bradley V. Stone BVS.Tools www.bvstools.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.