Dealing with errors during body stream reading

[cyruscollier]

Hey everyone! The API I'm using occasionally throws one of the following errors while using Node Fetch v3.2.4:

Invalid response body while trying to fetch https://[request URL]/: Premature close

Body used already for: https://[request URL]/

Request to https://[request URL]/ failed, reason: socket hang up ()

My implementation is very basic:

async request(context: RequestOpts, initOverrides?: RequestInit): Promise<Response> {
    const { url, init } = this.createFetchParams(context, initOverrides);
    const response  = await fetch(url, init);
    const body = await response.json();
    if (!response.ok) {
        const responseCode = response.status || 500;
        throw new Error(`${response.status} ${response.statusText} (${request.toString()})`)
    }
    return body;
}

The errors are infrequent, but show up enough in the production logs that I'm concerned, especially given the modest level of traffic to the site so far. The first error I've twice been able to somewhat reliably trigger it on one endpoint for a short period of time and then will go away after a period of time. The other two I haven't been able to reproduce at all. Here's what I do know:

1. All of the API responses are gzipped.
2. I'm pretty sure these errors only happen with GET requests.
3. Although there are no specific endpoints that trigger these errors, the Premature Close error does seem to happen more with requests that return larger response bodies, i.e. 25-100KB gzipped. It also might happen more when making several requests in a row and the API server is under slightly higher load (although still responding normally from what I see).

The ideas I have so far to solve this:

1. Update to latest version of Node Fetch (although I don't see anything new in 3.2.5-3.2.10 that seems relevant)
2. Add a keep-alive agent.
3. Add a simple retry in the case of these errors, perhaps with a 1-2 second backoff.
4. Re-implement using http response and gunzip streams with event emitters. I realize this isn't much different than what Node Fetch already does.
5. Contact the API provider and ask them for help, although at the moment I don't know anything specific to tell them since it's impossible to consistently reproduce and I don't think they'll know much about consuming their API with Node.js, as they are a .NET-based organization.

Thank you in advance for any other ideas you might have!