Go memory leak: Close your *http.Response Body!

Go’s documentation can sometimes wildly understate the importance of one of its warnings:

It is the caller’s responsibility to close Body. The default HTTP client’s Transport may not reuse HTTP/1.x “keep-alive” TCP connections if the Body is not read to completion and closed.

This warning seems to say that connection pools attached to a given *http.Client may not be reusable if you fail to close to

• go
• golang
• memory leak
• goroutine leak