In the current version, it is unable to set transport for http.Client.
If many connections and fast run, there is problem with ever-increasing TIME_WAIT socket on a network.
Creating and derivering http.client pointer may be one way, but to minimize modifications of origin code i just add http.Transport config to client.HTTPConfig.
I think It allows to handle http.Client Transport configurations about Connections at least.
In the current version, it is unable to set transport for http.Client. If many connections and fast run, there is problem with ever-increasing TIME_WAIT socket on a network. Creating and derivering http.client pointer may be one way, but to minimize modifications of origin code i just add http.Transport config to client.HTTPConfig. I think It allows to handle http.Client Transport configurations about Connections at least.