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 4590a497572d3070965dd2267d5bba6316a8ad15..b21b69e4b7a791a039d31b7b20b492e3b1fe38ea 100644 (file)
--- 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);