From e3d706e3d69be49cbe6576355fd8dcc5ac5e30a9 Mon Sep 17 00:00:00 2001
From: "Adam D. Ruppe" <destructionator@gmail.com>
Date: Mon, 29 Jan 2024 15:23:07 -0500
Subject: [PATCH] Prevent infinite loop on interrupted websocket

If a websocket message is split across continuation frames, it is
possible to get to this inner loop. If the browser is closed in the
middle of the message, the connection is closed, which makes the select
check return true, but then the other check returns false, indicating
eof, but the loop would continue.

We do not close the connection here, it just throws, but that's
consistent with other things for now. It should probably change too.
---
 cgi.d | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/cgi.d b/cgi.d
index ba83453..9bd2697 100644
--- a/cgi.d
+++ b/cgi.d
@@ -7080,8 +7080,10 @@ version(cgi_with_websocket) {
 				return false;
 			if(!isDataPending())
 				return true;
-			while(isDataPending())
-				lowLevelReceive();
+			while(isDataPending()) {
+				if(lowLevelReceive() == false)
+					throw new ConnectionClosedException("Connection closed in middle of message");
+			}
 			goto checkAgain;
 		}