On Sun, 27 Jan 2002, Tom Oehser wrote:
> I found the documentation on how to upgrade *modssl* later, using apxs.
> But that method doesn't seem to apply to upgrading *apache*...
The short answer is that while it *can* be done, it's a very manual
process and it's highly prone to mistakes. If you
On Sun, Jan 27, 2002, Tom Oehser wrote:
> [...]
> And, the mod_ssl I get from CVS is for 1.3.20, which is *less* than the
> one that is downloadable already built for 1.3.22, shooting holes in my
> initial theory that going to the CVS was even getting me closer to now...
Ops, my fault. The rsyn
P.S.
I found the documentation on how to upgrade *modssl* later, using apxs.
But that method doesn't seem to apply to upgrading *apache*...
-Tom
__
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User S
Dear all:
I have installed apache+mod_ssl+openssl on the windows 2000,and I also create the
server cert and key,and the apache with openssl can works well.
but when I want to configure the client authentication,it can not start.
my configure looks like:
SSLMutex sem
SSLRandomSeed sta
Dear all:
I have installed apache+mod_ssl+openssl on the windows 2000,and I also create the
server cert and key,and the apache with openssl can works well.
but when I want to configure the client authentication,it can not start.
my configure looks like:
SSLMutex sem
SSLRandomSeed sta
Is there a procedure that is known to be worth attempting to put a
modssl-X onto an apache-X+1?
Is there any intention or plan of releasing it within X days of the apache
release?
Is there any documentation of what is involved in doing it myself?
I saw mention of people having done it successf
you will need separate VirtualHost sections for both port 80 and port 443:
example (not real):
NameVirtualHost 10.10.10.10
Servername my.server.com
DocumentRoot /path/to/docs
ServerName my.server.com
DocumentRoot /path/to/htdocs
ServerAdmin [EMAIL PROTECTED]
(etc...)
On Sun, Jan 27
Jim Lee wrote:
> Response to Response:
> Yes, the Firewall is configured to allow port 443.
>
> In fact we are able to reach our web server from outside(internet) by typing
> in the following url.
>
> http://www.website.com:443
>
> But the moment we try the following url, it fails
>
> https:/
Response to Response:
Yes, the Firewall is configured to allow port 443.
In fact we are able to reach our web server from outside(internet) by typing
in the following url.
http://www.website.com:443
But the moment we try the following url, it fails
https://www.website.com
The same above step
