Best way to use HTTP client in a concurrent application

http go concurrency goroutine
Gonzalez picture Gonzalez · Apr 21, 2016 · Viewed 11.5k times · Source

First I'll describe my case. I have to do HTTPS requests to several APIs from my application and they should be ran concurrently. I want to know if I should use a separate HTTP client per goroutine or I can share one client across all goroutines. Of course I'd like to enjoy connection reusing/pooling offered by the HTTP client, but I am concerned about it being thread(aka goroutine)-safe and if the client will run requests concurrently or they'll in fact be sequenced?

Answer

william.taylor.09 picture william.taylor.09 · Apr 21, 2016

Http clients are thread safe according to the docs (https://golang.org/src/net/http/client.go):

Clients are safe for concurrent use by multiple goroutines.

Related questions

Correct way of getting Client's IP Addresses from http.Request

What's the correct way to get all client's IP Addresses from http.Request? In PHP there are a lot of variables that I should check. Is it the same on Go? One that I found is: req.RemoteAddr And is …

Read More
How to set headers in http get request?

I'm doing a simple http GET in Go: client := &http.Client{} req, _ := http.NewRequest("GET", url, nil) res, _ := client.Do(req) But I can't found a way to customize the request header in the doc, thanks

Read More
Make a URL-encoded POST request using `http.NewRequest(...)`

I want to make a POST request to an API sending my data as a application/x-www-form-urlencoded content type. Due to the fact that I need to manage the request headers, I'm using the http.NewRequest(method, urlStr string, body …

Read More