Just wanted to say thanks to everyone for the help in getting this going.
It turns out port 443 on our load balancer was not opened up. Now
everything is working.
Thanks again!
-----Original Message-----
From: Jennifer Dyess [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 05, 2000 12:24 PM
To: [EMAIL PROTECTED]
Subject: RE: how do you set specific pages to use ssl?
Well, I appreciate all the responses, but I must admit, I'm more confused
than ever!
When I try to browse https://www-dev.squaretrade.com/index_SSL.jsp, I get
"page cannot be displayed".
I am able to view the same page with just http://....
Apache is started w/ apachectl startssl and it starts up w/o any problems.
Here is my httpd.conf:
NameVirtualHost 172.168.250.99:80
<VirtualHost 172.168.250.99:80>
ServerName www-dev.squaretrade.com
Redirect http://www.dev-squaretrade.com/index_SSL.jsp
https://www-dev.squaretrade.com/index_SSL.jsp
DocumentRoot "/usr/local/apache/htdocs-dev"
</VirtualHost>
NameVirtualHost 172.168.250.99:443
<VirtualHost 172.168.250.99:443>
ServerName www-dev.squaretrade.com
DocumentRoot "/usr/local/apache/htdocs-dev"
SSLProtocol all
SSLCertificateFile /usr/local/ssl/certs/www-dev.squaretrade.com.crt
SSLCertificateKeyFile /usr/local/ssl/certs/www-dev.squaretrade.com.key
SSLLog /usr/local/apache/logs/ssl_engine_log
#SSLRandomSeed startup /dev/urandom 512
#SSLRandomSeed connect /dev/urandom 512
SSLLogLevel debug
SSLEngine On
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Brian T. Allen
Sent: Thursday, October 05, 2000 8:39 AM
To: [EMAIL PROTECTED]
Subject: Re: how do you set specific pages to use ssl?
If you are using a programming language, like PHP (which I use and love!),
you can set it up to detect whether it is port 80 or 443 and redirect as
necessary, avoiding the error message.
I have it set up so that if they view a page on port 80 that I want to be
viewed secure, it automatically redirects them to the same page on port 443.
Works nicely, and is transparent to the user. I do the oposite for the rest
of the site, so they don't surf the entire site on port 443 (more resource
intensive, slower).
> I believe you can restrict particular directories to only SSL access via
> the SSLRequire directive placed in the .htaccess file in the respective
> directories. Attempting to the access the directory or pages therein using
> HTTP results in an error.
>
> At 05:39 PM 10/04/2000 -0700, you wrote:
> >Are you refering to the actual html code or do you mean using redirect in
> >the httpd.conf?
> >
> >
> >
> >Call them as https://www.domain.com/page.html instead of
> >http://www.domain.com/page.html (note the addition of the "s").
> >
> >Brian
> >
> >
> > > It seems like such a simple thing, but I haven't been able to find a
clear
> > > answer on how to set directories and/or pages to require ssl.
> > >
> > > Any suggestions?
> > >
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
