My listen directives are as follows:
Port 80
<IfDefine SSL>
Listen 80
Listen 443
</IfDefine>
Also, as per your other email, I connected to :443 using openSSL, this
seemed to work, however, I still got a "Method Not Implemented" error.
Other than that, it seems to be reading the SnakeOil certs and server certs
and keys.
Tim Willis
IS Technician
Code Rite
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Mads Toftum
> Sent: Monday, May 15, 2000 15:02
> To: [EMAIL PROTECTED]
> Subject: Re: Mod_SSL Running...
>
>
> On Mon, May 15, 2000 at 11:53:27AM -0500, Tim Willis wrote:
> > ..but where?
> >
> > I'm able to start apache with mod_ssl, and the ssl_engine log
> verifies that
> > it has started, but when I go to https://localhost:443, it's not there.
> > Interestingly enough however, if I go to http://localhost:443, I get the
> > content from port 8080. I know that it's listening to both
> ports, but why
> > doesn't https work?
> >
> What does you Listen directives say? And what about the VirtualHost host
> directive - the latest versions of apache+mod_ssl will start on ports
> 8080 and 8433 if it is installed by a non root user.
> Note that both the http and https ports point to the same document root
> by default.
>
> vh
>
> Mads Toftum
> --
> `Darn it, who spiked my coffee with water?!' - lwall
>
> ______________________________________________________________________
> 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]
