From: Seonah Moon <seonah1.moon@samsung.com>
Date: Tue, 22 Nov 2022 07:22:23 +0000 (+0900)
Subject: h1: deal with WAITING_CONNECT in ops-h1
X-Git-Tag: accepted/tizen/unified/20221124.015426~1
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=cef400f67f6d06dd6e40093a79373b87462684ab;p=platform%2Fupstream%2Flibwebsockets.git

h1: deal with WAITING_CONNECT in ops-h1

We don't normally see events on the wsi in this state, but it is possible
since warmcat.com lwsws asserted on it in WAITING_CONNECT.

Explicitly handle it so we don't blow up.

https://github.com/warmcat/libwebsockets/commit/027fe42ceca78e04beb65d5c926cf6342e65acc8

Change-Id: I519fe91e10e97d140df7d3b65e79e73324535637
---

diff --git a/lib/roles/h1/ops-h1.c b/lib/roles/h1/ops-h1.c
index 4590a497..b21b69e4 100644
--- a/lib/roles/h1/ops-h1.c
+++ b/lib/roles/h1/ops-h1.c
@@ -292,6 +292,9 @@ ws_mode:
 		// assert(0);
 		/* fallthru */
 
+	case LRS_WAITING_CONNECT: /* observed on warmcat.com */
+		break;
+
 	default:
 		lwsl_err("%s: Unhandled state %d\n", __func__, lwsi_state(wsi));
 		assert(0);