Discussion in 'Plesk for Linux - 8.x and Older' started by serial-thrilla, Aug 10, 2005.
i noticed that the default setting for apache is to have keep-alive on. why does plesk turn it off?
Possibly for anticipated heavy traffic dynamic content webservers. Per the Apache docs: This is just a supposition on my part, who really knows why any SWSoft programmer does what (s)he does....
heavy dynamic content servers would not make a difference... keep-alives won't be used if the content length is unknown with http/1.0 however, i can't find any statistics on this, but i would safely say that almost everyone is now using http/1.1, because if they weren't using http/1.1, they wouldn't even be able to view the websites created using hostname based virtualhosts. now with http/1.1, we can use keep-alives with dynamic content because http/1.1 introduced chunked encoding. therefore, keep-alive should be on by default!
Good point, my brain totally skipped over the .0 part of the docs... my bad...
thanks and no prob
It looks like the Apache KeepAlive directive is set to Off by Red Hat, not by Plesk. Do you think it's safe to turn it on for all Plesk servers? Thanks.
i have. it made a nice improvement because it doesn't have to make another connection for each image on the page.
Separate names with a comma.