diamond (she/they)@beehaw.orgOPtoBeehaw Support@beehaw.org•Missing CORS prevents third-party web clientsEnglish
0·
1 year agoWebsocket handshakes are done over HTTP. The endpoint for Beehaw’s WS API would be wss://beehaw.org/
, so it’s still going to use the same CORS policies as accessing the /
(root) path.
Huh, interesting. It seems that a WS connection to
wss://beehaw.org/api/v3/ws
works, but notwss://beehaw.org
. I remember reading somewhere that the WS API will eventually be removed, though.I’ll continue development w/ the REST API until I feel like it’s in a mostly-working state, and then I’ll probably subject myself to the WS API after. Working with the REST API does feel a lot easier.