RE: [WEB400] Weird problem (IBM HTTP Original)

["Bartell, Aaron L. (TC)" <ALBartell@xxxxxxxxxxxxxx>]

>I don't understand how a single port can be "taken up by another domain
name".

Let me explain (even though my problem is resolved - see my other email).

Currently we have about 50 websites coming in through one ip address (I'll
call it .83).  Then our customers started demanding that our connections be
secure (SSL) so we started purchasing digital certificates.  We soon found
out that you can't have more than one digital certificate assigned to port
443 on the same IP address (at least under IBM Original HTTP server you
can't), so we started using up other ports for SSL purposes (8501, 8502,
8503, etc).  A couple months down the road some of our big customers changed
their networks and their users were only allowed to access secure sites that
used port 443.  That is what let to the moving of cso.cgintl.com from IP
address .83 to .89

To sum it up in a shorter sentence, we have a good handful of sites/domains
that all point to the same IP address (.83) but use a different port for SSL
services.

Whew.  Hope that made sense.

Aaron Bartell

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]On
Behalf Of Brad Stone
Sent: Tuesday, January 27, 2004 3:16 PM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Weird problem (IBM HTTP Original)


Aaron.

Your question is VERY confusing.  I don't understand how a
single port can be "taken up by another domain name".

Now, I do remember setting up the web pages you are talking
about, and I believe that each domain points to a single IP
which routes requests to your corporate firewall.  Then the
requests are routed inside to the AS/400 which has an
internal IP address.

I think the configs were set up using host names on the
configs.  Can't be sure, it's been a while.  But, still,
your question is making my head spin.  :)

Also, I seemed to be able to connect just fine.  So make
sure that your problem isn't because you have some local
DNS or host file causing problems.

You also may want to explain the setup... Internet domains,
IP addresses, firewall, iSeries, local IP addresses.  

Brad
www.bvstools.com

On Mon, 26 Jan 2004 14:21:03 -0600
 "Bartell, Aaron L. (TC)" <ALBartell@xxxxxxxxxxxxxx> wrote:
> Hi all,
> 
> I recently needed to move a domain
> (http://cso.cgintl.com) from one ip
> address to another because we needed to be able to use
> the default SSL port
> (443) which had already been taken up by another domain
> name.  The only
> thing in the config that I changed was the IP address
> from 999.999.999.83 to
> 999.999.999.89, and now the site doesn't come up - but
> the https does
> (https://cso.cgintl.com), which is obviously running off
> of the same config
> file.
> 
> We had our networking people make all the DNS changes and
> everything.  I can
> ping cso.cgintl.com and it responds with the correct IP
> address.
> 
> Anybody have any idea's for me of where I may have gone
> wrong?
> 
> Aaron Bartell
> _______________________________________________
> This is the Web Enabling the AS400 / iSeries (WEB400)
> mailing list
> To post a message email: WEB400@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/web400
> or email: WEB400-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the
> archives
> at http://archive.midrange.com/web400.
> 

Bradley V. Stone
BVS.Tools
www.bvstools.com
_______________________________________________
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.