|
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
Be the architects of evolution and help create the mobile internet future. It’s your move---enter to win here! |
|
#1
|
|||
|
|||
|
Hi guys I was just wondering a few things.
First which do you all find more functional and easier to use,set up, mod_ssl or ApacheSSL (is thare any diffrence)? Second does the Apache Groupe plan on adding built in SSL or TSL in to the newer releases? And Third what about SSL in the new Redhat web server? Thanks Sam. |
|
#2
|
|||
|
|||
|
1) Apache-SSL is more reliable and it gives you better performance but more resources will be used or wasted if you also run non-SSL. mod_ssl, on the other hand, is better for maintenance (you only get httpd.conf and httpd binary, not a separate httpsd.conf and httpsd). Say you've made some changes to httpd.conf, you don't need to sync that (by hand) to httpsd.conf.
2) No. Adding SSL takes significant amount of resources and it's not a wise thing to do for those who don't wish to enable SSL. 3) Redhat sucks. Why bother to install mod_ssl in RPM format and accept every default configurations (lose flexibility)? If you must stick with Redhat, grab the src and compile yourself. Finally, mod_ssl or Apache-SSL depends on what percentage of your site should be accessed via https. In mod_ssl, say you specify the following: MinSpareServers 5 MaxSpareServers 30 StartServers 5 and start it with apachectl startssl, 5 daemons will be started to handle BOTH SSL and non-SSL. In Apache-SSL, you need to start a whole new daemon httpsd and use httpsd.conf (a separate configure file). Say you start it with: MinSpareServers 5 MaxSpareServers 30 StartServers 5 If your https site doesn't need or you simply don't know how many server you should start, starting a fixed number of 5 might waste your system resources where you should have allocated it to httpd instead. That said, with mod_ssl, you can specify more server to start with and adjust the min and max to a higher value without worrying how much resource you should allocate for each. For example of httpd.conf (SSL+non-SSL): MinSpareServers 10 MaxSpareServers 60 StartServers 10 |
|
#3
|
|||
|
|||
|
Thanks for the help...
It sounds like in my case running ApacheSSL is a better option as I have a second server to run the SSL server on anyway. And It sounds like to me that Redhat wants to become the Microsoft of the Open source world with default configurations. What is next binary only distrobutions... Thanks for the help BSD. Cheers Sam |
![]() |
| Viewing: Dev Shed Forums > System Administration > Apache Development > SSL choices... |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|