go-cleanhttp alternatives and similar packages
Based on the "HTTP Clients" category.
Alternatively, view go-cleanhttp alternatives based on common mentions on social networks and blogs.
Go http.RoundTripper that emits open telemetry metrics. This helps you easily get metrics for all external APIs you interact with.
2.9 0.0 go-cleanhttp VS go-zoox/fetchGo Fetch - A Powerful, Lightweight, Easy Http Client, inspired by Web Fetch API
Do you think we are missing an alternative of go-cleanhttp or a related project?
Functions for accessing "clean" Go http.Client values
The Go standard library contains a default
http.DefaultClient. It is a common idiom in Go code to start with
http.DefaultClient and tweak it as necessary, and in fact, this is
encouraged; from the
http package documentation:
The Client's Transport typically has internal state (cached TCP connections), so Clients should be reused instead of created as needed. Clients are safe for concurrent use by multiple goroutines.
Unfortunately, this is a shared value, and it is not uncommon for libraries to assume that they are free to modify it at will. With enough dependencies, it can be very easy to encounter strange problems and race conditions due to manipulation of this shared value across libraries and goroutines (clients are safe for concurrent use, but writing values to the client struct itself is not protected).
Making things worse is the fact that a bare
http.Client will use a default
http.DefaultTransport, which is another global value
that behaves the same way. So it is not simply enough to replace
This repository provides some simple functions to get a "clean"
-- one that uses the same default values as the Go standard library, but
returns a client that does not share any state with other clients.