×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I wasn't referring to separate IP addresses for SSL vs. non-SSL. What I
was referring to is if you set up a server and tell it to listen on both
ports 80 and 443 and you are using SSL, the server doesn't work
properly. I forget what the exact problem is but I think if you do this,
SSL works and non-SSL doesn't. The fix (other than separate server
instances) is to use IP based virtual hosts so only the virtual host for
the SSL port tries to do the SSL handshake.
Matt
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of Scott Klement
Sent: Friday, October 05, 2007 4:22 PM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Multiple SSL certs and domains on same iSeries
You don't need to use separate IP addresses for SSL vs non-SSL because
they (usually) run on different ports. 80=Normal, 443=SSL.
matt.haas@xxxxxxxxxxx wrote:
Yes. You can also use this same technique to have SSL and non-SSL
traffic handled by the same server instance.
Matt
midrange.com
