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 gmail.com 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
--
This is the Web Enabling the AS400 / iSeries (WEB400)
mailing list
To post a message email: WEB400 midrange.com
To subscribe, unsubscribe, or change list options,
visit: htt
p://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request midrange.com
Before posting, please take a moment to review the archives
at http://archive.mi
drange.com/web400.
--
This is the Web Enabling the AS400 / iSeries (WEB400)
mailing list
To post a message email: WEB400 midrange.com
To subscribe, unsubscribe, or change list options,
visit: htt
p://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request midrange.com
Before posting, please take a moment to review the archives
at http://archive.mi
drange.com/web400.
|