Prevent upgrade to websocket connection

[matthewpflueger]

I want to prevent the upgrade request from succeeding if there isn't a valid authorization header on the request when handling the upgrade event. Unfortunately, there doesn't seem to be an obvious way to do this. Maybe I am taking the wrong approach? Here is what I have now:

function upgrade(input: Observable<Event>, ctx: EffectContext<unknown>): Observable<unknown> {
  return input.pipe(
    matchEvent(HttpServerEvent.upgrade),
    tap(ev => {
      if (!isAuthorized(ev.payload.request.headers.authorization)) {
        ev.payload.socket.write('HTTP/1.1 401 Unauthorized\r\n\r\n')
        ev.payload.socket.destroy()
      }
    }),
    mapToServer({
      path: '/api',
      server: ctx.ask(serverToken),
    }),
  )
}

This works fine initially but after some time, the entire server is killed due to a timeout:

debug: ServerListener OutgoingEvent stream completes {"tag":"websockets","service":"syncer","timestamp":"2021-07-16T17:21:48.190Z"}

node_modules/rxjs/dist/cjs/internal/util/reportUnhandledError.js:13
            throw err;
            ^
Error
    at _super (node_modules/rxjs/dist/cjs/internal/util/createErrorClass.js:7:26)
    at new TimeoutErrorImpl (node_modules/rxjs/dist/cjs/internal/operators/timeout.js:14:9)
    at timeoutErrorFactory (node_modules/rxjs/dist/cjs/internal/operators/timeout.js:60:11)
    at AsyncAction.<anonymous> (node_modules/rxjs/dist/cjs/internal/operators/timeout.js:37:34)
    at AsyncAction.<anonymous> (node_modules/rxjs/dist/cjs/internal/util/caughtSchedule.js:8:21)
    at AsyncAction._execute (node_modules/rxjs/dist/cjs/internal/scheduler/AsyncAction.js:76:18)
    at AsyncAction.execute (node_modules/rxjs/dist/cjs/internal/scheduler/AsyncAction.js:64:26)
    at AsyncScheduler.flush (node_modules/rxjs/dist/cjs/internal/scheduler/AsyncScheduler.js:39:33)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7) {
  message: 'Timeout has occurred',
  info: { meta: null, lastValue: null, seen: 388 }
}
error Command failed with exit code 1.

Any suggestions would be greatly appreciated!

[JozefFlakus]

The process could crash because of this thing: #345
It's worth checking if it still occurs.