| commit | 666a0c4d82674980598e649f6c2ea9d576778e3e | [log] [tgz] |
|---|---|---|
| author | Christopher Faulet <cfaulet@haproxy.com> | Tue Jan 08 11:12:04 2019 +0100 |
| committer | Christopher Faulet <cfaulet@haproxy.com> | Tue Jan 08 11:31:16 2019 +0100 |
| tree | d255d1345af2a09b8eb576409c4c88fa90049be0 | |
| parent | f3eb2b1c24d40ca745293a83a872d4e3f2b212c3 [diff] |
MEDIUM: mux-h1: Clarify how shutr/shutw are handled Now, h1_shutr() only do a shutdown read and try to set the flag H1C_F_CS_SHUTDOWN if shutdown write was already performed. On its side, h1_shutw(), if all conditions are met, do the same for the shutdown write. The real connection close is done when the mux h1 is released, in h1_release(). The flag H1C_F_CS_SHUTW was renamed to H1C_F_CS_SHUTDOWN to be less ambiguous. This patch may be backported to 1.9.