WebSocket fallback endpoint #658
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We do not need that feature anymore and it adds a lot complexity for every single API call that is being made
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
maybeast
requested changes
Aug 15, 2024
On regtest, when the backend is run without nginx and the WebSocket is on a different port than the rest of the API, we need to use a different endpoint for connecting to the WebSocket
michael1011
force-pushed
the
ws-fallback
branch
from
d95f5f8
to
8659a57
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.