Repository navigation
sse and multipart reconnection timeout for unresponse servers - #4099
Open
MichaelWest22 wants to merge 1 commit into
Open
MichaelWest22 wants to merge 1 commit into
MichaelWest22 wants to merge 1 commit into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
sse and multipart reconnections do not get the default connection timeout applied which means if the server fails to respond properly the connections can be left pending and never reconnect or try again. So we need to set a timeout here but this timeout may need to be shorter than the normal htmx default timeout of 60s. So I've added a new connectionTimout config for sse/multipart that defaults to the htmx default timeout but can be overriden if required.
Corresponding issue:
#4072
Testing
Added tests
Checklist
masterfor website changes,devforsource changes)
approved via an issue
npm run test) and verified that it succeeded