In this case it wouldn't matter because as soon as the browser hits the redirect, Apache is handling it. It wouldn't affect any other IIS sites, because this one would be on it's own. Glenn Hunt ghunt at hds.ca > -----Original Message----- > From: thelist-admin at lists.evolt.org > [mailto:thelist-admin at lists.evolt.org] On Behalf Of Scott Dexter > Sent: Monday, September 24, 2001 11:03 AM > To: thelist at lists.evolt.org > Subject: RE: [thelist] Piping Apache through IIS > > > > -----Original Message----- > > From: Glenn Hunt [mailto:ghunt at hds.ca] > > > > Probably the easiest thing is put a redirect on your IIS site: > > > > http://www.somedomain.com gets redirected to > > http://www.somedomain.com:8080. > > > > DUH. I'm over thinking. > > There's a bug (/I/ think it's a bug) with IIS though if you do this > route: IIS will add the port number to a URL that ends in a > directory without the trailing slash. So > http://www.w3rd.org/sgd turns into http://www.w3rd.org:8080/sgd/. If you include the trailing slash, IIS will leave the URL alone... --------------------------------------- For unsubscribe and other options, including the Tip Harvester and archive of TheList go to: http://lists.evolt.org Workers of the Web, evolt !