On Wed, Aug 11, 1999, [EMAIL PROTECTED] wrote:
> > > 203.67.11.65 - - [10/Aug/1999:13:15:48 +0800] "\200k^A^C^A" 501 -
> >
> > Your problem is just that you connect via HTTPS but on the target port only
> > HTTP is spoken. Your problem is that HTTPS is not enabled for the port. There
> > can be various configuration reasons. The most usual error is that the Listen
> > directives and the <VirtualHost> directives do not match. Or that another
> > <VirtualHost> is catching the port first. Or that `SSLEngine on' is missing
> > inside the HTTPS server's section. Check your config for those things.
>
> [...]
> I originally thought so. But I did carefully config the <VirtualHost> part.
>
> Eventually I did make it work. The problem was at one step:
>
> After configuring and compiling Apache, I need to "make certificate". But
> if I simply "make certificate; make install" , following the on-screen
> instruction, it doesn't work. I need to "make certificate TYPE=custom" to
> generate a server-useful certificate.
>
> I think at some step, there are some explanations on the screen about this.
> But it is not easy to see and figure out, or it is not even shown. The document
> didn't specify it clearly too.
>
> I highly recommend we should clearly include a sentence , like "use make
> certificate TYPE=custom if you want to use it on a web sever for testing",
> somewhere in the document and better in the configuration process.
Err... no, I cannot believe that your problem was related to the snake-oil
certificate. Instead I guess you've messed up something at the first attempt
and by coincidence did it right the second attempt. A different cert should
not cause any difference for the show problem.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
