Hi Ron,
Apache does not load the source file mod_ssl.c. Therefore there is no
need for it to know where the source is.
The filename (without path) is part of the module structure (coded in
by the define STANDARD_MODULE_STUFF) used to register handlers,
commands etc. of a module into the core
ComCity wrote:
Thank youAustin,Andy and Ron. I thought the purpose of the list was to
get helpI'm sorry if my question seemed stupid. It was not my intention
to post a stupid question in which I had not exhausted other resources or
throughly looked at what I could find on this.
Excuse me snipping all the old stuff, but I think I noticed from your logs
that you have managed to compile Apache 1.3.12 mod_ssl 2.6.6. against
openssl-0.9.6a, which in itself is quite an achievement. ie:
[Tue Oct 23 11:52:05 2001] [notice] Apache/1.3.12 (Unix) PHP/4.0.5
FrontPage/4.0.4.3
George,
Cool, thanks! Very good description of the need for this statement and
the errors it might invovle if certain proceedures are taken to restart
httpd and such. I guess the issue has never surfaced here as I have a
totally different proceedure for doing restarts after archiving logs and
Thank you.
- Original Message -
From: [EMAIL PROTECTED]
To: ComCity [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, October 23, 2001 11:25 PM
Subject: Re: New User: must be obvious question
Hi Mike,
the problem you are observing has a simple explanation. If you define
-DSSL
I'm having quite a perplexing problem, and I was hoping someone could give
me a hint here on this list.
First, my environment:
- Solaris 2.6
- Apache 1.3.20
- modssl 2.8.4
- openssl 0.9.6b
- Weblogic 5.1
- MSIE 5.5 sp1
I'm using apache to frontend WebLogic through a BEA provided module.
My
I've done a little more testing, and it seems like turning OFF the Show
friendly http error pages option in MSIE allows apache/mod_ssl to downgrade
the connection to HTTP/1.0 correctly. Turning it back on again leads to a
situation where it is NOT downgraded, and you get the server not found
On Wed, Oct 24, 2001 at 03:47:11PM -0700, Peter Morelli wrote:
I've done a little more testing, and it seems like turning OFF the Show
friendly http error pages option in MSIE allows apache/mod_ssl to downgrade
the connection to HTTP/1.0 correctly. Turning it back on again leads to a
Sorry, I have the same situation after using those config lines. I had seen
them on the mailing list before, but just to be sure I've just retested
them. No change. Same symptoms and solutions...
--pete
-Original Message-
From: David Rees [mailto:[EMAIL PROTECTED]]
Sent: Wednesday,
Any idea why this error is occuring?
[Wed Oct 24 15:45:29 2001] [notice] caught SIGTERM, shutting down
[Wed Oct 24 15:47:12 2001] [notice] Apache/1.3.22 (Unix) mod_ssl/2.8.5
OpenSSL
/0.9.6b configured -- resuming normal operations
[Wed Oct 24 15:47:12 2001] [notice] Accept mutex: flock (Default:
Those don't look like errors, just notices, or informational events. The
first one is apache shutting down, looks like from a kill command. The
second is Apache starting up again. No idea on the third. I get the first to
all the time in my error_log...
--pete
-Original Message-
From:
The problem is that SSL function.
R/Doug
Peter Morelli wrote:
Those don't look like errors, just notices, or informational events. The
first one is apache shutting down, looks like from a kill command. The
second is Apache starting up again. No idea on the third. I get the first to
all the
SSL doesnt function
Doug Dalton wrote:
The problem is that SSL function.
R/Doug
Peter Morelli wrote:
Those don't look like errors, just notices, or informational events. The
first one is apache shutting down, looks like from a kill command. The
second is Apache starting up again.
On Wed, Oct 24, 2001 at 05:38:40PM -0700, Peter Morelli wrote:
Sorry, I have the same situation after using those config lines. I had seen
them on the mailing list before, but just to be sure I've just retested
them. No change. Same symptoms and solutions...
And you do have a ssl session
14 matches
Mail list logo
