Haproxy开启keep-alive配置

原创

运维记事 2016-05-19 16:11:30 博主文章分类：Haproxy ©著作权

文章标签 keep haproxy alive 文章分类 运维

©著作权归作者所有：来自51CTO博客作者运维记事的原创作品，请联系作者获取转载授权，否则将追究法律责任

haproxy 1.5之后的版本支持5种连接方式

- KAL : keep alive ("option http-keep-alive") which is the default mode : all

requests and responses are processed, and connections remain open but idle

between responses and new requests. 默认的保持连接方式

- TUN: tunnel ("option http-tunnel") : this was the default mode for versions

1.0 to 1.5-dev21 : only the first request and response are processed, and

everything else is forwarded with no analysis at all. This mode should not

be used as it creates lots of trouble with logging and HTTP processing. HTTP隧道方式

- PCL: passive close ("option httpclose") : exactly the same as tunnel mode,

but with "Connection: close" appended in both directions to try to make

both ends close after the first request/response exchange. 关闭方式

- SCL: server close ("option http-server-close") : the server-facing

connection is closed after the end of the response is received, but the

client-facing connection remains open. 服务端关闭方式

- FCL: forced close ("option forceclose") : the connection is actively closed

after the end of the response. 强制关闭方式

说下强制模式(option forceclose)：

HTTP 1.1默认情况下是使用保持连接方式，只要启用了option httpclose,服务器就会向客户端发送Connection:close.但是某些浏览器不认这个http-header，依然会采用保持连接方式，这个时候服务器如果配置option forceclose就会自动在连接完成后进行关闭。

所以如果需要开启keep-alive就只需要配置

option http-keep-alive

option http-server-close

timeout http-keep-alive 10s

timeout client 30s

#option nolinger #如果发现TIME_WAIT过多的时候开启这个参数可以及时清理一些TCP连接，但是也会出现“连接被重置”，慎用

关闭keep-alive

option httpclose

option forceclose

#option nolinger

对比Connection:close