On Fri, Mar 24, 2000, jleung wrote:
> We have Apache 1.3.12 with mod_ssl-2.6.1-1.3.12, and secure and non-secure
> web server running on the same Solaris box. The SSL had been working fine
> for weeks before the system rebooted a couple of days ago. Now, we
> couldn't connect to the secure server, and the following is the error
> message it logged into the error_log:
>
> [error] [client x.x.x.x] Invalid method in request C
> [error] [client x.x.x.x]Invalid method in request F
>
> and for the access_log, its says:
>
> - - [24/Mar/2000:11:04:51 -0800] "F" 501 -
>
> Do you know what could be the problem here? We did start and stop the
> secure server before with the system up and running with no ill effects.
> Now, does it mean that we need to test the secure server with a system
> reload as well?
This has nothing to do with a reboot. If it worked before, someone has
changed your server config. The problem you have is that you're speaking
HTTPS to a port where only HTTP is spoken. There can be various reasons.
the most common reason is that the Listen and <VirtualHost> directives
do not exactly match or that an "SSLEngine on" is missing in the HTTPS
virtual server part. Check your server configuration, please.
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]
