fix(realtime): omit authorization header when no access token exists #1937
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
summary
when using the
realtime restfallback without a session, the client sends an empty authorization header which causes a 500 error from the server.problem
the rest fallback in
httpSend()andsend()always includes anauthorization header, even when no token exists. this results inAuthorization:(empty value) being sent, which the server rejects with 500.fix
only add the authorization header when
AccessTokenValueis truthy. the server accepts requests with just theapikeyheader.closes #1936 & #1590
supersedes #1561
cc @mandarini