Here's something that caused me to switch from apache-ssl to mod_ssl in less than a heartbeat:
Apache 1.3.14 was released, and an update to apache-ssl for this new version cannot be found (perhaps I am REALLY blind). Mod_ssl has the update already. Now why would I want to continue running apache 1.3.12 just because this Ben person is slow to posting a new patch? Got me..
Also, although I've had problems with both apache-ssl and mod_ssl previously (newbie disease), mod_ssl was a much easier install than apache-ssl (having to deal with openssl include directories not being found automagically by apache-ssl's configure, numerous other edits by hand had to be done to get it working as well).
Another plus for mod_ssl is that it is able to be compiled as loadable module, making upgrades easier.
After using both, it seems to me like Ben is just reinventing the wheel when his efforts could more than likely be more productive if focused on the modssl project.
Slashdot Mirror
Apache 1.3.14 was released, and an update to apache-ssl for this new version cannot be found (perhaps I am REALLY blind). Mod_ssl has the update already. Now why would I want to continue running apache 1.3.12 just because this Ben person is slow to posting a new patch? Got me..
Also, although I've had problems with both apache-ssl and mod_ssl previously (newbie disease), mod_ssl was a much easier install than apache-ssl (having to deal with openssl include directories not being found automagically by apache-ssl's configure, numerous other edits by hand had to be done to get it working as well).
Another plus for mod_ssl is that it is able to be compiled as loadable module, making upgrades easier.
After using both, it seems to me like Ben is just reinventing the wheel when his efforts could more than likely be more productive if focused on the modssl project.