Home
Feed

Extend

Hashnode Pro
Hashnode for Agents

Resources

The foreword
Hashnode gql skill

Buildful - AI coding agent that delivers frontier-level results at a fraction of the cost Bug0 - The AI-native e2e QA regression testing Hackathons Changelog Brand @hashnode on X Hashnode on LinkedIn Support - hello+support@hashnode.com Code of Conduct Terms Privacy Sitemap

Search Hashnode

Search posts, tags, users, and pages

Discussion on "WebSockets in RedwoodJS" | Hashnode

Feed/

Discussion

Tobbe Lundberg

Fullstack developer with a focus on the technical frontend

Feb 25, 2023

WebSockets in RedwoodJS

Realtime/WebSocket support in Redwood has been requested since forever*. For most people, using something like https://pusher.com/channels or https://supabase.com/docs/guides/realtime is the best choice. But I wanted to see if I could roll my own. (*...

tobbe.hashnode.dev8 min read

#redwoodjs #websockets #react-context

Responses2

Markdown supported · ⌘↵ to post

Nick F

Apr 5, 2023

Thanks for the answer. Another question, do you know why wss doesn't pass authentification token into backend handler, so we can't authentificate the request?

I don't think WebSockets does that. Have a look at this StackOverflow question and read the answer and the comments on the first question stackoverflow.com/questions/4361173/http-headers-…

Tobbe Lundberg

Fullstack developer with a focus on the technical frontend

Apr 6, 2023

Nick F

Apr 4, 2023

Great article, thank you. But how is it possible to define backend url for WebSocket object? You hardcode it here, but not clear, how to define it on frontend dynamically.

Tobbe Lundberg

Fullstack developer with a focus on the technical frontend

Apr 5, 2023

For my experiment I didn't bother figuring that out. But when I deployed my example app I did change it to wss://app-url.com/.redwood/functions/ws to get around CORS limitations (where .redwood/functions/ is proxied to my api side by my hosting setup, just like all graphql requests are proxied)