The WebSocket context assumes the handshake request and response objects can be used after the handshake is performed

Our default WebSocket context implementation relies on stub HTTP request and response objects that wrap the WebSocket handshake request and response objects. Depending on the servlet container implementation, the WebSocket handshake request and response objects might become stale, and thus unusable after the handshake is performed, i.e. once we end up in the WebSocket end-point (which often needs to use the WebSocket context).

See https://github.com/jetty/jetty.project/issues/11809 for a related problem. This problem was caught on the Jakarta migration branch, where the new version of Jetty seems to have changed the behavior concerning the WebSocket handshake request and response objects.