> From: Valter Nogueira [mailto:[EMAIL PROTECTED]] > Subject: RE: [JBoss-user] Virtual Hosts > > What you mean is that we can't refer directly to IP address, > as I usually do > when developing, and I should config a hosts file (or DNS) to > assign apps to > IP and use the app name.
yes, that is correct. > Just one more thing. > > My IIS is configured to the address 10.1.1.1 port 80. Can I > make Jetty > respond to the virtual ip 10.1.1.2 port 80 on the same > machine? or does > Jetty respond to all IPs avaiable? Or does it just respond to > 10.1.1.1 and > finish? If IIS is already on port 80, you won't be able to have Jetty on it. If you had Apache on port 80, you could put a connector in so that one of your virtual hosts was connected to Tomcat, but I don't think you can do this with Jetty, and also not sure if you can do this on Windoze. I would suggest is to ignore the details of the last paragraph and simply use another port (such as 8080), then use urls such as http://myhost1:8080/context/page.html. Vhost doesn't care about port, it's up to the client to connect to the same port as the server is running on. Since the client sends the name of the server it is trying to get to over HTTP 1.1, irrespective of port, whatever server is sitting on the port will properly vhost if it is set up correctly. Then you can set things to port 80 when you go to production. That's what I do. Setting up the listening port is done in the jetty-service.xml or tomcat-service.xml file in the deploy dir, depending on which you are using. -b ------------------------------------------------------- This SF.NET email is sponsored by: Order your Holiday Geek Presents Now! Green Lasers, Hip Geek T-Shirts, Remote Control Tanks, Caffeinated Soap, MP3 Players, XBox Games, Flying Saucers, WebCams, Smart Putty. T H I N K G E E K . C O M http://www.thinkgeek.com/sf/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
