I did some more research to try to get a sense of the timeline and have
found that the EAPI in Apache has been available since at least 1.3.14 (the
docs are a little vague on when it was introduced). Apache is now on
version 1.3.20.
The specific problem that we are having is that mod_ssl requires EAPI
support and seems to have required after mod_ssl 2.6 (now on 2.8.4). OpenSA
(an apache based package for Win32) provides support for Apache, Cold Fusion
and mod_ssl but seems to be frozen at Apache 1.3.12/Mod_SSL 2.6. I suspect
that this is due to the lack of EAPI support for CF being in conflict with
the EAPI requirement on mod_ssl.
CF runs fine with all the current builds of apache using the standard API,
but if one wants to run SSL, then mod_ssl is required and thus EAPI is
required and thus Cold Fusion is using the wrong API (of mod_ssl is using
the wrong API, depending on your point of view).
So the bottom line appears to be that to support SSL on Apache and run Cold
Fusion, you need an EAPI build of the Cold Fusion module, which according to
Macromedia is only going to be available in 5. I have yet to install 5 to
see if this is true.
Does anyone else run SSL on Apache with Cold Fusion on Win32 and if so, how
did you resolve this issue?
Justin
--
Justin Greene
ClicVU, Inc. - Makers of the Spamex Disposable Email Address Service
P: 212-242-0258
http://www.spamex.com
Sign up for your free Spamex account:
Protect your real email address forever
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
