Security fix
WebSocket upgrade listener leaves non-WebSocket Upgrade requests open, leading to socket exhaustion
Affects: applications that use the websocket option. The upgrade listener ignored requests whose Upgrade header was not websocket, so the socket stayed open until the client closed it. A client could hold many connections open this way, and clients that try an HTTP/2 upgrade over plain HTTP hung. GHSA-8wcc-wqxr-28qp
Such a request is now answered with 400 Bad Request and the socket is closed, unless the application registers its own upgrade listener.
Full Changelog: v2.1.9...v2.1.10