SuperTokens is an open source authentication solution offering features like: Different types of login: Email / password, Passwordless (OTP or Magic link based).

SuperTokens.com

```
backend_2         | 2023/03/16 13:36:52 http: response.WriteHeader on hijacked connection from github.com/supertokens/supertokens-golang/supertokens.SendNon200Response (utils.go:188)
backend_2         | 2023/03/16 13:36:52 http: response.Write on hijacked connection from github.com/supertokens/supertokens-golang/supertokens.(*basicWriter).Write (doneWriter.go:69)

```

Perhaps <@908641146379579433> can help out

I hope so, do you know when he could be online?

hi <@390974869162164255> could you share a bit more details? what are you trying to do? which framework are you using?

<@908641146379579433> did you read the other messages from <@390974869162164255> ?

this issue seems to happen when the supertokens middleware tried to respond on the connection that was upgraded to websocket. could you share details on you production setup? do you have specific routes set up to be upgraded to websocket ?

The thing is that we have same setup on dev as on prod

I would say let's have a call together so i could show you the code?

yes sure, we can - plz book a call here - https://calendly.com/sattvik-supertokens/30min , or we can talk now

plz check now, it should show slots for today

hi <@390974869162164255> , I had a quick word with <@498057949541826571> , cookie based auth is not the right thing to do for the websockets. It's best you use JWT based auth and then pass the token as a message after the websocket connection is established and validate that on the backend.