commit | 81fdeb8ce2cb10bfe2119dbb4c63f080bb5f8be4 | [log] [tgz] |
---|---|---|
author | Christopher Faulet <cfaulet@haproxy.com> | Thu Feb 16 16:47:33 2023 +0100 |
committer | Christopher Faulet <cfaulet@haproxy.com> | Wed Feb 22 14:52:14 2023 +0100 |
tree | d7f0f9ebc9c02bebd882567874be8117c51a3706 | |
parent | 3ffbf3896d6e6d6bef99763957fb67fb9023cce3 [diff] |
MEDIUM: channel: Remove CF_READ_NOEXP flag This flag was introduced in 1.3 to fix a design issue. It was untouch since then but there is no reason to still have this trick. Note it could be good to review what happens in HTTP with the server is waiting for the end of the request. It could be good to be sure a client timeout is always reported.