Skip to content

Conversation

@7ttp
Copy link
Contributor

@7ttp 7ttp commented Dec 9, 2025

summary

when using the realtime rest fallback without a session, the client sends an empty authorization header which causes a 500 error from the server.

problem

the rest fallback in httpSend() and send()always includes an authorization header, even when no token exists. this results in Authorization: (empty value) being sent, which the server rejects with 500.

fix

only add the authorization header when AccessTokenValue is truthy. the server accepts requests with just the apikey header.

closes #1936 & #1590
supersedes #1561

cc @mandarini

@7ttp 7ttp requested review from a team as code owners December 9, 2025 15:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

REST Fallback for Realtime Broadcast Sends Empty Authorization Header, Causing 500 Error

1 participant