Can a DO initiate a websocket connection?

1. Hey, can't remember about the DO storage limits regarding key and value size: are they the same as KV's? 2. And to confirm, calling a DO via as stub from another DO counts as part of the global sub-requests limitations? Which is then 50 calls? Thanks!

Not sure, I believe someone already asked this question on the discord, something with some standard websocket class not supported -feel free to use the search! 🙂

+1 I'm currently having to implement a workaround that same limitation

1. key 2048 bytes, value 32KiB https://developers.cloudflare.com/workers/runtime-apis/durable-objects#transactional-storage-api

dang me! I read that section like 10 min ago, just totally avoided the put() section

(got stuck on the "limitation" section of the doc)

Yes - I saw that the Websocket constructor has not been implemented - was wondering if WebSocketPair in DO had some functionality to replicate it..

If you make a request using

fetch()

and set the header

Upgrade: websocket

, the system will automatically add the other stuff to perform a WebSocket handshake. If the server fulfills its end of the handshake, then the response object will have a

webSocket

member. Call

.accept()

on it to indicate you wish to handle it locally, and then you can call

send()

and add event handlers like normal.

cc @User

Thanks @kenton. Appreciate your help.

(obviously we need to get that documented somewhere....)

Woo

Heck yess

im adding this to CFW-EU asap

doesnt seem this API is available in Workers, is this a DO only feature?

no, it should work for everyone

ah then maybe my nearest PoP doesnt support it yet

ok so, this is what im running into right now

js
  var url = 'wss://echo.websocket.org'
  var resp = await fetch(url, { headers: {'upgrade': 'websocket'} })
  // resp.webSocket is null

the URL needs to be http I think

remember you're upgrading from http to wss, not connecting to wss directly

I may also be wrong, and it could be that websocket.org doesn't support

wss

, just

ws

.

thats the example URL they give

and i can confirm it works

however changing it to HTTPS doesnt change the situation

Yeah, the example URL they give is for the living standard WebSocket API, which does the http -> ws upgrade step for you as part of the connection process:

To establish a WebSocket connection, given a url, protocols, and client, run these steps:
    Let requestURL be a copy of url, with its scheme set to "http", if url’s scheme is "ws", and to "https" otherwise.

either way, doesnt seem to be working

from what i can tell, CF is intercepting the websocket connection and throwing a 502 in its place