Why Doesn\'t the Go HTTPS Client Reuse Connections by Default?

Why Go HTTPS Client Does Not Reuse Connections

In this discussion, we explore an issue where the Go HTTPS client fails to reuse connections, leading to potentially problematic behavior.

Problem Description

The provided Go code creates multiple connections to a particular host, despite using a single http.Transport instance with DisableKeepAlives set to false. This is unlike similar Python code using the requests library, which reuses connections.

Understanding the Issue

The initial misunderstanding was that the Go client should reuse connections by default. However, further clarification revealed that the default behavior requires the response to be closed before connections can be reused.

Solution

To ensure HTTP connection reuse in Go, two essential steps must be taken:

1. Read until the response is complete (e.g., use ioutil.ReadAll(resp.Body))
2. Close the response body (i.e., resp.Body.Close())

Additional Considerations

While the lack of maximum connection control is a limitation, it can be mitigated by rate-limiting requests using time.Tick.

Conclusion

By addressing the issue of closing the response body, developers can ensure that Go's HTTP client properly reuses connections. This is crucial to avoid accumulating excessive TCP connections.

The above is the detailed content of Why Doesn't the Go HTTPS Client Reuse Connections by Default?. For more information, please follow other related articles on the PHP Chinese website!