754 - Clean up EventSource when the page is closed/reloaded #755
+4
−0
Conversation
This file contains hidden or 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
|
I keep running into this as well. We have a page that executes an XHR call to a subsequent resource and I've noticed the occasional hang as the browser runs into its SSE connection limits. |
ofipify
approved these changes
Apr 21, 2025
Author
|
Any chance this gets merged? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes issue 754
This is a very basic fix but it works.
I did try to implement a more robust handling of the SSE connection on the server side as well (SSE heartbeats, lowering TCP timeouts), but could not get it to work reliably without also risking making the proxy far less transparent.