bodyclose
July 23, 2026 ยท View on GitHub
bodyclose is a static analysis tool which checks whether res.Body is correctly closed.
Install
You can get bodyclose by go get command.
$ go get -u github.com/timakin/bodyclose
How to use
bodyclose run with go vet as below when Go is 1.12 and higher.
$ go vet -vettool=$(which bodyclose) github.com/timakin/go_api/...
# github.com/timakin/go_api
internal/httpclient/httpclient.go:13:13: response body must be closed
Options
You can enable additional checks with the -check-consumption flag to also verify that response bodies are consumed:
$ go vet -vettool=$(which bodyclose) -check-consumption github.com/timakin/go_api/...
Handled Response Directive
Use //bodyclose:handled on a function that fully handles every returned
*http.Response body before returning:
// bodyclose:handled
func doRequest(req *http.Request, handle func([]byte) error) (*http.Response, error) {
resp, err := http.DefaultClient.Do(req)
if err != nil {
return nil, err
}
defer resp.Body.Close()
body, err := io.ReadAll(resp.Body)
if err != nil {
return nil, err
}
if err := handle(body); err != nil {
return nil, err
}
resp.Body = io.NopCloser(bytes.NewReader(body))
return resp, nil
}
Calls to an annotated function are skipped by both the close and consumption checks, including calls from another package.
The directive works only for statically resolved function calls.
Supported Consumption Patterns
When -check-consumption is enabled, the following patterns are recognized as valid body consumption:
io.Copy(io.Discard, resp.Body)io.ReadAll(resp.Body)ioutil.ReadAll(resp.Body)(legacy)json.NewDecoder(resp.Body)bufio.NewScanner(resp.Body)bufio.NewReader(resp.Body)
Limitations and False Positives
Note: Patterns not listed above may trigger false positives even when the body is properly consumed. Use //nolint:bodyclose to suppress warnings for custom consumption patterns that are not automatically detected.
Example of suppressing false positives:
func customBodyProcessing() {
resp, _ := http.Get("http://example.com/") //nolint:bodyclose
defer resp.Body.Close()
// Custom consumption logic that analyzer doesn't recognize
buf := make([]byte, 1024)
resp.Body.Read(buf) // This actually consumes the body
}
Limitation: The analyzer does not detect execution order, so patterns where Close() is called before consumption (which would fail at runtime) are not specifically flagged.
Legacy Usage (Go < 1.12)
When Go is lower than 1.12, just run bodyclose command with the package name (import path).
But it cannot accept some options such as --tags.
$ bodyclose github.com/timakin/go_api/...
~/go/src/github.com/timakin/api/internal/httpclient/httpclient.go:13:13: response body must be closed
Analyzer
bodyclose validates whether *net/http.Response of HTTP request calls method Body.Close() such as below code.
resp, err := http.Get("http://example.com/") // Wrong case
if err != nil {
// handle error
}
body, err := ioutil.ReadAll(resp.Body)
This code is wrong. You must call resp.Body.Close when finished reading resp.Body.
resp, err := http.Get("http://example.com/")
if err != nil {
// handle error
}
defer resp.Body.Close() // OK
body, err := ioutil.ReadAll(resp.Body)
In the GoDoc of Client.Do this rule is clearly described.
If you forget this sentence, a HTTP client cannot re-use a persistent TCP connection to the server for a subsequent "keep-alive" request.