5
Missing CORS prevents third-party web clients
(beehaw.org)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 17 Jun 2023
5 points (100.0% liked)
Beehaw Support
2797 readers
1 users here now
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.
founded 2 years ago
MODERATORS
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/wsworks, 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.
Right. I was reading a code snippet from somewhere else where they called into the root path, but the library that they were using probably did the appending in the background which I didn't know.
There is an issue upstream tracking this. For now, I only mostly use Beehaw, so that's fine.
Nope, I'm using
lemmy-js-client. The WS part of it doesn't do much, so I didn't bother using it. TheLemmyWebsockettype wasn't also in the main import for some reason, but that wasn't much of an issue.