``` backend_2 | 2023/03/16 13:36:52 http: response.WriteHeader on hijacked connection from g...
r
Copy code
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)
r
Hey @rob197
Perhaps @sattvikc can help out
r
I hope so, do you know when he could be online?
r
Tomorrow morning (IST time zone)
Around 11 am IST
r
ok thanks
s
hi @rob197 could you share a bit more details? what are you trying to do? which framework are you using?
r
@sattvikc did you read the other messages from @rob197 ?
s
no, I just saw this thread. let me check
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 ?
r
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?
@sattvikc
s
yes sure, we can - plz book a call here - https://calendly.com/sattvik-supertokens/30min , or we can talk now
r
You have no slot for today
s
I do, available till 5 pm IST
plz check now, it should show slots for today
r
comming now
s
yes please
hi @rob197 , I had a quick word with @rp_st , 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.
r
Ok thanks
14 Views