Try introduce connection idle-timeout #204
Closed
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
zorglube
force-pushed
the
reverse-proxy-IdleTimeout
branch
from
85fb9a9 to
86cb60b
Compare
zorglube
force-pushed
the
reverse-proxy-IdleTimeout
branch
from
2aacc0f to
de0d358
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.
Since I use Clever-Cloud to host MovieNight I have some
2024-02-29T21:23:02+01:00 [ERROR] 2024/02/29 20:23:02 Could not copy video to connection: write tcp 10.2.130.190:8080->185.42.117.109:37002: write: broken pipe.As far as I understood it come from the
IdleTimeoutduration of the connection pool used into MovieNight.So I open a possibility to set this idle timeout.