On Wed, 11 Feb 2026 20:37:36 GMT, Josiah Noel <[email protected]> wrote:
> To me it makes sense to treat it like any other request that takes an > extended amount of time. I'm not sure what kind of timeouts you both are talking exactly, is it read/write timeout or general timout of the overall connection exchange? Because at least WebSocket can keep the connection "forever", and as we do not know the "upgraded protocol" I would say the implementer is responsible for setting up any timers to close a connection after some idle period (e.g. alive messages, maximum response times ...) ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/27989#discussion_r2796744355
