|
That is a good way to solve the multiple ports issue but gets expensive if you want to run HTTPS on each domain and so need a certificate for each. >>> albartell@xxxxxxxxx 3/21/2006 9:16 PM >>> >> I've been looking through the examples and haven't been able to figure >> out how to not require the port. The reason I ask is that I see in >> some of my examples that don't use port 80, that the configured port >> is not specified. The direction I like to go sometimes is to use sub domains so you don't have to start going the port route. For instance, http://sub.domain.com/ is much more appealing than http://domain:8080/. Not that URLs have to be appealing, but sometimes image matters :-) Aaron Bartell
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.