exogen / exogen/node-fetch-har

Support for aborted and timed out requests

Open
#12 1 comment 0 reactions 0 assignees View on GitHub
bug
Dominant language
JavaScript
Stars
34
Forks
3
PR merge metrics
No merged PRs in 30d

Description

Right now, if there is no response (for example, if the request is timed out or aborted), no entry will be added to the HAR log.

This means you get no visibility into these requests – you could see things long a long period of no network activity, and then a succesful retry request. But there actually was network activity, it was just a timed out request.

I'm not sure how aborted and timed out requests are represented in HAR files but will have to generate such requests in Chrome to find out.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.