When I accidentially started Apache-1.3.3 + mod_ssl_2.1.0 as an ordinary user,
I got:
Syntax error on line 418 of /opt/apache/conf/httpd.conf:
SSLCertificateKeyFile: file not exists or empty
/opt/apache/sbin/apachectl startssl: httpd could not be started
Exit 3
Well, I don't tota
Ralf S. Engelschall wrote:
>
> SSL_SSLEAY_VERSION). These are all passed to fpexe when called through
> SSL, along with all the other normal env vars that are passed to fpexe
> durring a working non-SSL call. So one might come to the conclusion
> that these extra env vars throw up some warning
On Wed, Nov 18, 1998, Ben Laurie wrote:
> > Please be technical only and correct. The assertions were not just removed in
> > mod_ssl. They were replaced with run-time checks which pass the error up to
> > the callers and there it's handled without and exit().
>
> I don't understand the distinct
On Wed, Nov 18, 1998, Manuel J. Galan wrote:
> I've uploaded apache-1.3.3/mod_ssl-2.1.0 to
> contrib site.
>
> Builds and installs flawlessly in an Apollo (RH5.2) system.
>
> If you have other addon modules (php3, ...) maybe you will
> have to recompile those.
Interesting, then the other RH5.2
On Thu, Nov 19, 1998, Anthony Rumble wrote:
> OK.. first.. using the Bog standard apache/1.3.3 with modperl/1.15 that
> comes with RedHat 5.2.. (also using a cookie based authentication module)
> works fine.. no problems..
>
> Thu Nov 19 00:44:06 1998] [notice] Apache/1.3.3 (Unix) (Red Hat/Linu
I've uploaded apache-1.3.3/mod_ssl-2.1.0 to
contrib site.
Builds and installs flawlessly in an Apollo (RH5.2) system.
If you have other addon modules (php3, ...) maybe you will
have to recompile those.
__
Apache Interface to SSL
OK.. first.. using the Bog standard apache/1.3.3 with modperl/1.15 that
comes with RedHat 5.2.. (also using a cookie based authentication module)
works fine.. no problems..
Thu Nov 19 00:44:06 1998] [notice] Apache/1.3.3 (Unix) (Red Hat/Linux)
mod_perl/1.15 configured -- resuming normal operatio
Ralf S. Engelschall wrote:
>
> On Wed, Nov 18, 1998, Ben Laurie wrote:
>
> >[...]
> > > My $0.02, if it's worth anything. But if that's the way you code
> > > Apache-SSL, I'm very glad my friend pointed me to mod_ssl.
> >
> > If you want to use a system where programming errors are "corrected"
now children!
--
simon
__
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
On Wed, Nov 18, 1998, Ben Laurie wrote:
>[...]
> > My $0.02, if it's worth anything. But if that's the way you code
> > Apache-SSL, I'm very glad my friend pointed me to mod_ssl.
>
> If you want to use a system where programming errors are "corrected" by
> removing the assertions that reveal t
SPASTIC Member wrote:
>
> 127.0.0.1 is just another interface. All possible errors can happen.
> Imagine a server where the load is high enough that other processes don't
> get to run much... they write to localhost, expecting what's on the other
> end to get it, but the localhost interface buff
On Wed, Nov 18, 1998, Philp Gwyn wrote:
> On 18-Nov-98 Ralf S. Engelschall wrote:
> > Fine, nice to hear this. I'm very curious about how good (or bad?
> > ;-) 2.1 runs on real production systems. We'll see... when problems
> > occur we'll fix it as fast as possible.
>
> Don't you have a product
127.0.0.1 is just another interface. All possible errors can happen.
Imagine a server where the load is high enough that other processes don't
get to run much... they write to localhost, expecting what's on the other
end to get it, but the localhost interface buffers overflow.
Or the misconfigur
Here I forward a message from c.i.w.s.u posted yesterday. The poster talks
about Apache+mod_ssl+mod_frontpage and the fact that SSL works fine, FP works
fine, but the combination SSL+FP fails because some environment things caused
by mod_ssl (perhaps the SSL* env vars, whatever) seems to confuse
On 18-Nov-98 Ralf S. Engelschall wrote:
> Fine, nice to hear this. I'm very curious about how good (or bad?
> ;-) 2.1 runs on real production systems. We'll see... when problems
> occur we'll fix it as fast as possible.
Don't you have a production system to test on? Or are you developing
this f
Philp Gwyn wrote:
>
> On 17-Nov-98 [EMAIL PROTECTED] wrote:
> > Some further information: At the office, with an ethernet
> > connection to the server, the problem never happens. I've tested
> > Netscape 3.0, Navigator 4.06, and Communicator 4.06. At home,
> > with Netscape 3.02, it's quite co
On Wed, Nov 18, 1998, Philip Gwyn wrote:
> On 17-Nov-98 Ralf S. Engelschall wrote:
> >
> > Happy birthday! The 2.1.0 tarball is rolled and released. Either
> > it now horribly fails or succeeds, but at least it's now out. The
> > official Announcement is appended below. Thanks to all who
> >
On 17-Nov-98 Ralf S. Engelschall wrote:
>
> Happy birthday! The 2.1.0 tarball is rolled and released. Either
> it now horribly fails or succeeds, but at least it's now out. The
> official Announcement is appended below. Thanks to all who
> contributed to the project and made the release of 2.1
On 17-Nov-98 [EMAIL PROTECTED] wrote:
> Some further information: At the office, with an ethernet
> connection to the server, the problem never happens. I've tested
> Netscape 3.0, Navigator 4.06, and Communicator 4.06. At home,
> with Netscape 3.02, it's quite consistent. This is going over
Some further information: At the office, with an ethernet connection
to the server, the problem never happens. I've tested Netscape 3.0,
Navigator 4.06, and Communicator 4.06. At home, with Netscape 3.02,
it's quite consistent. This is going over a PPP connection.
When I change the CGI script
Full_Name:
Version: 2.1.0
OS: Linux
Submission from: bilbo.fto.de (193.197.153.9)
make in apache directory:
<=== src/os/unix
===> src/ap
gcc -c -I../os/unix -I../include -DLINUX=2 -DMOD_SSL=201100 -DUSE_HSREGEX
-DEAPI `../apaci` ap_execve.c
In file included from ../include/httpd.h:82,
21 matches
Mail list logo
