Canceled DO WebSocket Connection
Good Day!
Transitioning our fully functional WebSockets to DO w/ hibernation.
Problem: the DO and client now never make the connection.
Controller
It looks like the return of the request isn’t either sent, as the status on the front end only goes from Closed to Connecting back to Closed, or it’s not accepted or rejected by the client?
Because webSocketClose is triggered, the CF documentation says “the client closes the connection” then “runtime will invoke the webSocketClose() handler”, is the client rejecting or resting the connection?
Something glaringly wrong (embarrassing
) with what we’ve setup?
Transitioning our fully functional WebSockets to DO w/ hibernation.
Problem: the DO and client now never make the connection.
Controller
It looks like the return of the request isn’t either sent, as the status on the front end only goes from Closed to Connecting back to Closed, or it’s not accepted or rejected by the client?
Because webSocketClose is triggered, the CF documentation says “the client closes the connection” then “runtime will invoke the webSocketClose() handler”, is the client rejecting or resting the connection?
- Service side the routing is handled by Hono, but WebSockets work fine outside DOs and can see with logs the request is making it to the DO.
- On the client side we are using react-use-websocket ?? Can’t find anything that WebSockets with DOs should be handled any differently..
Something glaringly wrong (embarrassing