|
Sorry to dredge up an old thread, but I was researching the archives and found something that may solve my problems, but I don't really understand how to implement the suggestion. Rob Berendt mentioned that he has multiple Domino servers on a single 400 and doesn't want to use separate ports. Brad Stone suggested the following: PASS /* /first/* www.first.com (or 192.23.4.55) PASS /* /second/* www.second.com (or 192.23.4.56) And I have some questions: Did that work? Where do you add the PASS directives? WRKHTTPCFG? The httpd.cnf files for your various Domino servers? Elsewhere? Do you have to have different IP addresses for the different servers? Here's our particular situation: We have Domino listening on Port 80, and the IBM HTTP Server listening on 8080. This is causing us some trouble, because some companies' firewalls/proxy servers won't allow http traffic on anything but 80 to come through. So I'd like to have both listen on 80. I'd like: www.estes-express.com to point to the IBM HTTP Server and domino.estes-express.com to point to the Domino Server I want to keep using the Domino server to serve Domino databases, but I want to use the IBM HTTP Server to do everything else (right now the IBM server is only running Net.Data and RPG CGI programs). And I can't put them on separate IP addresses. Is what I want even possible? If so, is it practical? Mike Eovino E-commerce and Customer Development Manager Estes Express Lines http://www.estes-express.com +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.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.