fix(server): harden HTTP server timeouts#249
Open
samcm wants to merge 2 commits into
Open
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.
The main HTTP server had no
IdleTimeoutorReadTimeout, a 3 minuteReadHeaderTimeout, and a 15 minuteWriteTimeout. Idle keep-alive connections were never reaped, and a slow reader could hold a response (and its memory) for up to 15 minutes.This sets
IdleTimeoutto 120s,ReadTimeoutto 60s, dropsReadHeaderTimeoutto 30s, and lowersWriteTimeoutto 5 minutes. The write timeout stays generous because beacon state downloads are hundreds of MB and can legitimately take minutes on slow links.