feat: add WrapTransport option
#505
Merged
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
for custom transport middleware. This enables users to wrap the underlying `http.RoundTripper` with custom middleware without losing the default transport configuration (fastdialer, TLS settings, connection pooling). The wrapper function receives the default transport and returns the transport to use. It is applied to both HTTP/1.1 and HTTP/2 clients. Closes #504. Signed-off-by: Dwi Siswanto <[email protected]>
Mzack9999
approved these changes
Dec 15, 2025
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.
feat: add
WrapTransportoptionfor custom transport middleware.
This enables users to wrap the underlying
http.RoundTripperwith custom middleware withoutlosing the default transport configuration
(fastdialer, TLS settings, connection pooling).
The wrapper function receives the default
transport and returns the transport to use. It is
applied to both HTTP/1.1 and HTTP/2 clients.
Closes #504.