Hello,
brief info:
got apache + mod_ssl(DSO) + mod_perl(DSO) + mod_frontpage(DSO) work!
Solution: compile everything with '-fPIC'
history and explanation:
Several people ran into problems with running apache and mod_ssl as
DSO unter Solaris, causing a SEGV within SSLeay after the first
res
Hello Edward,
> In my setup, I am not interested in logging SSL connections, so
> I used the directive
>
> SSLLog /dev/null
>
This should be the default (as with other Log-directives within apache),
so just omit the SSLLog configuration command or place a '#' before it.
Jan
Hello Victor,
as the cited begger for DSO I might argue at this:
> Hm.
> 1. Why you need two httpd servers in first place ?
Because to avoid heavy memory consumption for all customer servers.
> 2. How much is memory penalty for not-used mod_ssl ?
>
That's not the point; If you want to be
Hello,
I just tried to compile a SSL-patched (mod_ssl-2.0.13) apache version,
but *without* activating mod_ssl:
gcc -c -I../../os/unix -I../../include -DSOLARIS2=251 -DMOD_PERL
- -DUSE_HSREGEX -DSERVER_SUBVERSION=\"PHP/3.0.3\" -O2 -DFPX_CORE_PATCH
- -I/usr/local/include `../../apaci` proxy_
Hello again,
> > There are also missing some conditional Makerules, to prevent
> > to make the certificate stuff, if mod_ssl is disabled.
>
> Hm `make certificate' needs to know SSL_BASE and other stuff. This is
> only calculated when mod_ssl is actually enabled. So there is no chance to
Sorry for german stuff on this list;
mail should go directly to Ralf.
__
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manage
Hi,
in my test environment I got it running:
apache-1.3.3, fully modularized with additional share modules:
mod_frontpage, mod_perl and or course: mod_ssl :-)
Ralf: As I mailed you (and by accident to the list) before
concerning the problems while patching the source against
1.3
Hello Sam,
because you asked on the list, I will answer here too:
(sorry for the inconvenience to other readers)
> I thought that mod_frontpage required a patch similar to
> mod_ssl--Could you please give me a description of how you got
> this to work.
At least I did some more patch
Hello Ralf,
I got the following problems, partly by configuration mistake
(on that other machine, where I did have the problems with another
compiled apache and mod_perl, but no longer have this kind of),
and detected the following:
- If the SSLLog path/directory does not exist, there's no error
Hi,
> Ralf, Tom, and others, I've gotten another clue to my non-working web server.
> As you may recall, everything seems to have compiled correctly, but hitting
> my website:
>
> https://mymachine.foo.com:8443/
>
It's the additional port nr. '8443' which confuses mod_ssl.
the same hap
> Wait! On _ALL_ my testings on en1.engelschall.com I use port 8080 for HTTP an
> d
> 8443 for HTTPS because en1 also runs the non-testing Apache+mod_ssl on 80/443
> .
Well, now I got the message and may explain the behaviour
(which I tried before)
I (and also the other writer to the list) made
Sorry Folks,
I have been stucked up by some projects for the last two weeks...
but anyway I don't know a sulotion to the problems described.
We're mostly using Thatwe Certificates which are at least
not accepted by Frontpage itself.
So we're not able to test Frontpage over SSL :-(
Jan
_
Hi,
> UID 0 based processes? Perhaps then you have to run it on ports 8080/8443
> temporarily as a regular user to get the core. Without the coredump and a
> backtrace it's hard to find the location of the SIGSEGV.
>
Thanks for the hint, Ralf.
Meanwhile I got some closer and got at least a cor
h perl-5.004_04, but with =
>
> a freshly installed perl-5.005_02 it core-dumps.)
>
> Greetings,
> Jan
>
>
>
Mit freundlichen Grüßen / best regards,
UUNET Deutschland GmbH
Jan Wedekind
Manager Techn. Op. Web/Services UUNET Deutschland
14 matches
Mail list logo
