Generally, you shouldn't need to change your httpd.conf, but if you do, this page is to share tips & tricks about Tiki-related configs.
Note also that some hosting services do not allow you to change the httpd.conf file, because it may be shared between different accounts running on the same web server. In those cases, some of the configuratesions suggested below can still be done by putting them in the .htaccess file.
On some slow servers (or heavily shared server farms like BlueHost), this can add several seconds to the loading time of every page. To avoid this, you must set an expiry date on files which are of a static type. On this type of server, this technique has been known to shave off a couple of seconds from the loading time of pages.
# time out connections earlier, 300 is too much Timeout 150 # clients may keep alive existing connections KeepAlive On MaxKeepAliveRequests 120 KeepAliveTimeout 15 !Starting more than one children # switch off hostname lookups, that needs some time HostnameLookups Off MinSpareServers 6 MaxSpareServers 8 StartServers 10 # 10 clients should be enough, but for peaks 50 might be good. # depends on your memory, 50 works for 2GB memory MaxClients 50 # dont set this to a value too low: MaxRequestsPerChild 1500
Limit connections from one ip to a given number.
Homepage of mod_limitipconn
<IfModule mod_limitipconn.c> Customlog /var/log/nameofvirtualhost-access-denied.log combined env=LIMITIP <Location /> MaxConnPerIP 10 NoIPLimit img/* </Location> </IfModule>