I've posted previously about compile problems with Apache 2.0.47 on W2K.
I've got those issues resolved now, and can compile Apache with SSL
My question is, do you have any recommendations on "best practices" for
setting up Apache + SSL + W2K + OpenSSL? Here are the steps I'm
considering, but am open to better ideas:
1. Install the Apache pre-built binaries from www.apache.org, namely
2. Install OpenSSL from either a)
with the other tools I'm using (awk, bison, flex, and sed from the cygwin
3. Download the Apache source code
4. Download the OpenSSL source code and install under
5. Compile OpenSSL and Apache using the defaults. This will install Apache
as C:\Apache2 and create mod_ssl.so file. openssl.exe will be under
6. Copy Apache2 directories and files from C:\Apache2 to C:\Program
Files\Apache Group\Apache2, which is where the pre-built binary is
installed. But, keep the *.conf files from the original, pre-built binary
7. Delete all openssl files from the Apache directories. They are
redundant - use the cygwin version of OpenSSL.
This may be overkill, or I may be making this too hard. But, even
Apache.org recommends using the pre-built binaries for installation on
Windows, but then fails to create a pre-built binary supporting SSL (for
export reasons I presume). I suppose I can forego the pre-built binaries
for both Apache and OpenSSL, just compile and install Apache/OpenSSL, and
just manually create the Apache service, Program Group links, etc. that the
pre-built binaries create.
Or, is it as simple as just copying mod_ssl.so from C:\Apache2\... to
C:\Program Files\Apache Group\Apache2\...?
Which is the whole purpose of this post :-). If you have any
recommendations for best practice to follow for installing Apache with SSL
support under W2K, please let me know.