Hi, just tried 0.20 on NT4; I like it! I ran into some problems,
both minor and not-so-minor.
1. MINOR PROBLEM: The binary distribution is missing the mime.types file,
so you can't run Apache until you snarf a copy of the file from somewhere
else. No biggy, but it would be nice to have it already there.
2. WISH-LIST: It'd be nice to have some way to install opensa as an NT service
and simultaneously specify if SSL is turned on or not (it would save hacking
up the httpd.conf file to remove the IfDefine SSLs).
3. NASTY PROBLEM: Repeated reloads of an SSL connection between Netscape
and the 0.20 server seem to cause the SSL engine to die and restart.
This is a serious pain, to say the least.
More details:
Client: Navigator 4.08 on Win98, with a valid client certificate.
Server: OpenSA 0.20 on NT4 with a self-signed certificate. PHP4 not loaded.
ASP not loaded. Server is running as an NT service.
Process: - Make a successful SSL connection between client and server
(the first time Netscape goes through all the steps of dealing
with the new site certificate).
- Netscape will pop up a window asking you to select a user
certificate. Sometimes this will work the first time and
you won't notice a problem. The problem might only appear if
you reload the page several times (I'm using the default top-level
server page from the 0.20 distribution as a test case). When the
problem does appear, Netscape keeps asking you to select a
certificate.
- On the server, you'll see a popup window (not always the first time,
sometimes only after the reload attempts) with the following message
(and the addresses don't appear to change):
Apache.exe - Application Error
The instruction at "0x10030778" referenced memory at "0x3152575e".
The memory could not be "read".
- If I look at the logs, the only indication of a problem is that the
engine.log has added another "You are using mod_ssl under Win32"
warning message.
Notes: I've tested both with and without an SSL session cache, no impact on
the problem either way. I also tested with IE 5 and the same client
certificate; this time I couldn't make the problem appear at all.
Whatever is going on seems to be specific to Netscape.
Any ideas?
