On Wed, May 30, 2001 at 11:04:41AM -0400, Firas wrote:
> I actually got the right certificate, so i'm sure that ssl over http was
> enabled
> This is really strange.
yeah, this is strange, so may I throw in an equally strange idea:
Could it possibly be that you have two different versions of apache
running, e.g. one started during system bootup and the other one
started by yourself manually? As long as they run on different ports
they wouldn't interfere. And the apache with the apparently working
SSL might not be the one you think it is.
May sound a little far-fetched, but things like these do happen
occasionally... Additional hints in this direction are the fact that
there's the JServ module mentioned in the startup notice in the
error_log, though you never configured that in. Along the same lines,
in the message it says mod_ssl/2.8.4, but you configured 2.8.2 ...
So, just assuming this were the case, then it could still be that you
get the error message for the SSLRequireSSL directive, because mod_ssl
is not loaded (as has already been pointed out).
As far as I can tell from your original post, you configured mod_ssl
as a DSO module, meaning that the shared object file needs to get
loaded in httpd.conf. So you might want to check whether you have the
required lines somewhere in httpd.conf:
LoadModule ssl_module modules/libssl.so
AddModule mod_ssl.c
If you started out modifying some default config file, then they might
already be in there, possibly enclosed in <IfDefine SSL>...</IfDefine>.
Btw, did you start apache with "apachectl startssl"? (the 'startssl'
arg causes the startup script to pass a '-DSSL' to httpd, which in
turn activates everything wrapped by <IfDefine SSL>...)
All this may be utter garbage -- but just in case you run out of things
to try ;)
Anyway, good luck!
- Almut
> ----- Original Message -----
> From: "Owen Boyle" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, May 30, 2001 10:17 AM
> Subject: Re: Invalid command 'SSLRequireSSL'
>
>
> > Firas wrote:
> > > You were right the module isn't loaded, but how come I can access the server
> > > throught https ??
> >
> > I guess you actually defined a non-SSL virtualhost on port 443 and so
> > the traffic was really plain HTTP... (did you get all the certificate
> > dialogue?)
> >
> > > That's strange, I checked apache's logs and I've got a bunch of these :
> > >
> > > error_log:[Wed May 30 08:54:41 2001] [notice] Apache/1.3.20 (Unix)
> > > ApacheJServ/1.1.2 mod_perl/1.25 PHP/4.0.5 mod_ssl/2.8.4 O
> > > penSSL/0.9.6a configured -- resuming normal operations
> >
> > Weird. The only difference I can see in your compilation is that I did:
> >
> > ./configure \
> > --with-apache=../apache_1.3.20 \
> > --with-ssl=../openssl-0.9.6 \
> > --prefix=/full/path/to/apache
> >
> > i.e. I gave an argument to --with-ssl and defined the apache prefix...
> >
> > Rgds,
> >
> > Owen Boyle.
> > ______________________________________________________________________
> > 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]
