On Mon, Oct 05, 1998, Michael Lechner wrote:
[...]
That was my approach too - however you should change your
installation instructions:
o Create the all-in-one SSLeay Makefile for building under Win32:
$ perl util\mk1mf.pl no-asm dll VC-WIN32 makefile.win32
On Mon, Oct 05, 1998, Alan Spicer wrote:
Red Hat Linux 2.0.34
Apache 1.3.1
SSLeay-0.9.0.b
mod_ssl-2.0.10-1.3.1
[...]
I changed the "VirtualHost _default_:443" to:
VirtualHost xxx.xxx.xx.xxx:443
and added my virtual host settings in there, and left
everything else alone. The certificate
Ralf S. Engelschall wrote:
Ok, I make you an offer: Create a temporary rse account on your box which has
around 15 MB free disk space available and I'll try to setup Apache on your
box and debug the code on your specific platform. I'm sure it's a local
platform problem, but we cannot find
James H.G. Redekop wrote:
Ralf S. Engelschall wrote:
I've compared his config file with the default config. Just harmless path
differences. And his config file runs fine (after changing the paths, of
course) for my with Apache 1.3.2 + mod_ssl 1.3.2. Seems I've now even to build
with
In article you wrote:
[...]
*I* believe that the user takes ALL responsibility for getting
free and open source software working. I also believe that
this is the nature of free software. Others have already said
that it does work and are trying to help. It is inappropriate
for
In article you wrote:
Ralf S. Engelschall wrote:
Ok, I make you an offer: Create a temporary rse account on your box which has
around 15 MB free disk space available and I'll try to setup Apache on your
box and debug the code on your specific platform. I'm sure it's a local
platform
