|
You could use rewrite rules to redirect to your SSL site. The only time this may cause a problem is if you're posting data and specify the full host name in the method you're posting to. If you're entire site is running under SSL, something like this would fix all of your links: <VirtualHost 127.0.0.1:80> DocumentRoot /www/foo/htdocs ServerName foo.myco.com UseCanonicalName On HostNameLookups off RewriteEngine on RewriteOptions inherit RewriteRule ^/(.*) https://foo.myco.com/$1 [L,R] </VirtualHost> You can also narrow this down to certain virtual directories or even individual documents if you wanted to. Matt -----Original Message----- From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta Sent: Tuesday, March 28, 2006 5:45 PM To: 'Web Enabling the AS400 / iSeries' Subject: Re: [WEB400] Using a Verisign Certificate for SSL Thanks, Matt! That was exactly the issue that needed to be fixed. A simple one line addition in the admin page and everything is up and running. Now, however, I have to start looking at other bits and pieces like anyplace where "http:" is hardcoded and some other issues with IP addresses. But the server is up and running with SSL! Thanks for everyone's help! Joe > From: Matt.Haas@xxxxxxxxxxx > > 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.