0
Missing CORS prevents third-party web clients
(beehaw.org)
Support and meta community for Beehaw. Ask your questions about the community, technical issues, and other such things here.
A brief FAQ for lurkers and new users can be found here.
Our September 2024 financial update is here.
For a refresher on our philosophy, see also What is Beehaw?, The spirit of the rules, and Beehaw is a Community
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
[This comment has been deleted by an automated system]
Websocket 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.
[This comment has been deleted by an automated system]