On Sat, Apr 29, 2000, Daniel S. Reichenbach wrote:
Thanks for your patches. But I personally cannot decide whether these
are reasonable and correct or not. Can someone else confirm that these
patches are really necessary for mod_ssl to build under Win32? I'm still
very sceptic whether
hello,
i can get an authorization for me to accept a self-generated CA and server
certificates
and i hit yes, and i'll get nothing after that
any reasons for this?
i'm not sure whether they have a fix out/or coming out with one, but any
information would be helpful
in the apache conf:
SetEnvIf
Addressed to: [EMAIL PROTECTED]
alles kapot [EMAIL PROTECTED]
** Reply to note from alles kapot [EMAIL PROTECTED] Fri, 28 Apr 2000 21:22:59 -0700
(PDT)
I did several compiling testing to see which php3 module caused the
Segmentation fault.
first I compiled whithout any
I have heard a way to hack netscape browsers to add my custom CA cert into
Netscape's browser, so that certs signed by my CA can be recognized as
super-certs. Unfortunately, I didn't find simlar info in the archive, does
any one know about that?
BTW: I'm not on the list, please reply to my
Hi,
I have solved this problem on my own. The error was that the Port
directive still was "Port 80", but it has to be "Port 443" in such a
configuration.
Tim
--
Tim Niemueller [EMAIL PROTECTED] www.niemueller.de
Ok, but then the question remains: Why was this extra include and this
extra lib not necessary in the past to build Apache+mod_ssl under Win32
and why is it still not necessary for some users while users say it is?
Apache required Winsock 2 from version 1.3.9 on, maybee thats the magic
point.
Hi,
Are there any sources which describe how the Apache 2.0 API
will affect future mod_ssl integration?
In particular we are interested in how the EAPI might be affected
since we are currently implementing a module which leverages
the client 'hooks' in the EAPI.
Thanks,
Stuart Zakon
