Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311)

> That leaves "finalize response". I suppose that for some network errors (in particular CORS) there could be a successful body stream so this would come later. For others that might not happen. Either way, we probably want to report them as soon as possible (i.e., as part of "fetch finale") to avoid leaking timing information. (Which also means "finalize response" (or its callers) has to filter out network errors or some such.)

Are you suggesting to omit the timing entry if the network error comes after the body stream has been opened?
I don't think it leaks any information. The fetch client knows when they get the `error` event, and the timing entry should correspond to that.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/1311#issuecomment-932863885