feat: Make TCP inactivity timeout configurable #7910
+33
−8
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
Make TCP inactivity timeout configurable
Previously, mitmproxy used a hardcoded TCP inactivity timeout of 10 minutes (600 seconds) for all TCP connections. This change makes the timeout configurable through a new
tcp_timeout
option, allowing users to adjust the timeout based on their specific use cases.Changes:
tcp_timeout
option tomitmproxy/options.py
with default value of 600 secondsmitmproxy/proxy/server.py
to use the configurable timeout instead of hardcodedTCP_TIMEOUT
mitmproxy/tools/cmdline.py
test/mitmproxy/test_options.py
Usage:
This change maintains backward compatibility by keeping the same default timeout value while providing the flexibility to adjust it for different network environments and use cases.
Checklist