]> git.ipfire.org Git - thirdparty/haproxy.git/commit
MEDIUM: mux-h1: Clarify how shutr/shutw are handled
authorChristopher Faulet <cfaulet@haproxy.com>
Tue, 8 Jan 2019 10:12:04 +0000 (11:12 +0100)
committerChristopher Faulet <cfaulet@haproxy.com>
Tue, 8 Jan 2019 10:31:16 +0000 (11:31 +0100)
commit666a0c4d82674980598e649f6c2ea9d576778e3e
treed255d1345af2a09b8eb576409c4c88fa90049be0
parentf3eb2b1c24d40ca745293a83a872d4e3f2b212c3
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.
src/mux_h1.c