Re: Using a Verisign Certificate for SSL

Joe,

You need to modify your virtual host so it listens on port 443. By
default, it listens on port 80 and a couple of other ports that were set
up when the instance was generated.

Matt 

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of Joe Pluta
Sent: Tuesday, March 28, 2006 4:37 PM
To: 'Web Enabling the AS400 / iSeries'
Subject: Re: [WEB400] Using a Verisign Certificate for SSL

Hot snarkies!  By adding the virtual host as shown below (and no
NameVirtualHost entry), I do indeed get the appropriate SSL access!
Both
the SSL and the non-SSL requests (both via IP and via DNS name) get
routed
properly.  My only problem now is that the WebSphere requests are not
getting intercepted by the WebSphere plug-in.  My guess is that there's
probably something in my WebSphere configuration that needs to be set
correctly to route the HTTPS requests the same way it routes the HTTP
requests.

Thanks everyone for helping this far.  We're getting close!

Joe

> From: Alfredo Delgado
> 
> If you add the following lines, I would expect https://10.20.30.40/ to
> take you to the same place http://10.20.30.40/ does.
> 
> <VirtualHost 10.20.30.40:443>
>    SSLEngine On
>    SSLAppName QIBM_HTTP_SERVER_MYINSTANCE
> </VirtualHost>