proxy: initialize ReverseProxy.Transport earlier and fix TCP connection leak #2134
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.
1. What does this change do, exactly?
Fix a bug introduced in 98de336, #2070
98de336#diff-a71769529a289e215ba922059611256bL309
Before 98de336,
proxy
usedhttp.DefaultTransport
for every request.After 98de336,
proxy
creates a newhttp.Transport
for every request.Then
caddy
will create a lot of TCP connections and won't reuse them.I found this because
github.com/transmission/transmission
can only have 1024 file descriptors, And it encounters errortoo many files open
frequently when I upgradedcaddy
to 0.10.13.2. Please link to the relevant issues.
See 1.
3. Which documentation changes (if any) need to be made because of this PR?
None.
4. Checklist