On Wed, Jan 20, 1999, [EMAIL PROTECTED] wrote:
>[...]
> Upgrading from apache 1.2.6+ben'ssl to 1.3.4 + mod_ssl 2.1.7
> has caused me a fair bit of grief - everything seems fine
> (i'd done the upgrade on Solaris boxes with no problems)
> but as soon as i try and connect to the https port through my
> browser, I get :
>
> httpd: [Wed Jan 20 15:32:58 1999] [error] [client 130.194.2.70] Invalid method
> in request @
> httpd: [Wed Jan 20 15:36:17 1999] [error] [client 130.194.2.70] Invalid method
> in request k
>
> I went back and got mod_ssl 2.0.15 (and apache 1.3.3) and it all
> seems to work ok. But it seems something's up with 2.1.x that
> stops it working on Digital Unix somehow ?
>
> I'm using SSLeay 0.9.0b too.
Sounds like your HTTP connect reaches a non-SSL-enabled port on your server.
Make sure the "SSLEngine on" is in place and that the <VirtualHost> really
matches the Listen directives and your IP addresses.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
