Httpd KeepAlive: Difference between revisions
No edit summary |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 19: | Line 19: | ||
Setting [[Httpd KeepAliveTimeout#Overview|KeepAliveTimeout]] to a high value may cause performance problems in heavily loaded servers. The higher the timeout, the more server processes will be kept occupied waiting on connections with idle clients. For more details on this see [[HTTP Persistent Connections#Disadvantages|HTTP Persistent Connections Disadvantages]]. | Setting [[Httpd KeepAliveTimeout#Overview|KeepAliveTimeout]] to a high value may cause performance problems in heavily loaded servers. The higher the timeout, the more server processes will be kept occupied waiting on connections with idle clients. For more details on this see [[HTTP Persistent Connections#Disadvantages|HTTP Persistent Connections Disadvantages]]. | ||
A HTTP/1.1 client will automatically benefit from the persistent connection settings, and will get a persistent connection configured as per the content of KeepAlive, [[Httpd KeepAliveTimeout|KeepAliveTimeout]] and [[Httpd MaxKeepAliveRequests| MaxKeepAliveRequests]]. A HTTP/1.0 client should explicitly declare that it wants a persistent connection, as described here: [[HTTP/1.0 Persistent Connections]]. | |||
Latest revision as of 23:26, 8 January 2017
External
Internal
Overview
"KeepAlive" specifies whether or not to allow persistent connections (more than one request per connection). Set to "Off" to deactivate.
... KeepAlive Off ...
Setting KeepAliveTimeout to a high value may cause performance problems in heavily loaded servers. The higher the timeout, the more server processes will be kept occupied waiting on connections with idle clients. For more details on this see HTTP Persistent Connections Disadvantages.
A HTTP/1.1 client will automatically benefit from the persistent connection settings, and will get a persistent connection configured as per the content of KeepAlive, KeepAliveTimeout and MaxKeepAliveRequests. A HTTP/1.0 client should explicitly declare that it wants a persistent connection, as described here: HTTP/1.0 Persistent Connections.