Thanks Kevin for these insights. It does seem like the documentation
notes were meant for Go core devs. It would have helped, if the
authors threw in more insight.
I have also been using RoundTripper as client middleware, but so far
largely for authentication. I wanted to expand the scope of the
I'll make an attempt to answer this question but I could be wrong given
some deeper historical context between the early Go developers.
There are two chunks of the http.RoundTripper comments that folks typically
ask about: "should not attempt to handle higher-level protocol details" and
"should
I am trying to understand in what cases would it make sense to
implement my own RoundTripper.
If I search about it, I come across examples of RoundTripper that try
to do things like caching, retries, authentication, etc. I also read
somewhere that there are many RoundTripper implementations that
