]> git.ipfire.org Git - thirdparty/squid.git/commit
Do not send keep-alive in 101 (Switching Protocols) responses (#709)
authorAlex Rousskov <rousskov@measurement-factory.com>
Mon, 10 Aug 2020 18:46:02 +0000 (18:46 +0000)
committerSquid Anubis <squid-anubis@squid-cache.org>
Wed, 12 Aug 2020 18:48:38 +0000 (18:48 +0000)
commit18ce34b290020c79943bcdaba5debcce568e57f0
treeecfbbf1307ec443f218237b6a1875ccda5439dd9
parent983fab6e9ea971228eeb6e09ab55bedf113d1d7b
Do not send keep-alive in 101 (Switching Protocols) responses (#709)

... because it breaks clients using websocket_client[1] library and is
redundant in our HTTP/1.1 control messages anyway.

I suspect that at least some buggy clients are confused by a multi-value
Connection field rather than the redundant keep-alive signal itself, but
let's try to follow RFC 7230 Upgrade example more closely this time and
send no keep-alive at all.

[1] https://pypi.org/project/websocket_client/
src/servers/Http1Server.cc