workaround for node.js bug https://github.com/nodejs/node/issues/21398

[timotab]

There's a bug in the version of Node.js 10.x that Lambda uses that causes the http request 'end' event to not be fired. see https://github.com/nodejs/node/issues/21398

This results in the "close" and therefore "total" timings to be the timeout value, instead of the actual URL load end value. Example graph (with calculated items to change from milliseconds to seconds) shows the results for www.google.com as I adjusted the timeout values: 6s, 10s, 30s, 60s.

Workaround listed on the nodejs issues page applied to this code fixes the problem.