You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given that http.Client already provides a RoundTripper interface for injecting custom logic into the HTTP request/response flow (e.g., for logging, retries, modifying headers, etc.), what are the primary use cases or architectural considerations where it would be more beneficial or necessary to define and use a custom HttpRequestDoer interface instead of simply relying on or extending http.Client's existing capabilities?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
Given that
http.Client
already provides aRoundTripper
interface for injecting custom logic into the HTTP request/response flow (e.g., for logging, retries, modifying headers, etc.), what are the primary use cases or architectural considerations where it would be more beneficial or necessary to define and use a customHttpRequestDoer
interface instead of simply relying on or extendinghttp.Client
's existing capabilities?Beta Was this translation helpful? Give feedback.
All reactions