Re: [whatwg/fetch] Add response status to response body info (PR #1468)

@abinpaul1 commented on this pull request.



> @@ -301,6 +301,9 @@ following <a for=struct>items</a>: [[RESOURCE-TIMING]] [[NAVIGATION-TIMING]]
  <dt><dfn export for="response body info" id="fetch-timing-info-decoded-body-size">decoded
  size</dfn> (default 0)
  <dd>A number.
+ <dt><dfn export for="response body info" id="fetch-timing-info-response-status">response

Okay, just to be sure I understand. We would pass in the status as a new parameter to [Mark resource time](https://w3c.github.io/resource-timing/#dfn-mark-resource-timing) which would in turn pass it to [Setup the resource timing entry](https://w3c.github.io/resource-timing/#dfn-setup-the-resource-timing-entry) where we would use it to set the entry's `responseStatus`.

> Also, as we talked on the Chromium CL, I don't think we should automatically make this TAO-protected rather than CORS-protected. It's not exactly timing information.

Yeah, we don't want to. I am a bit unsure as to how we would would specify this in the specification . I initially thought mentioning in the Note in [Cross-origin Resources section of resource timing](https://w3c.github.io/resource-timing/#sec-cross-origin-resources) that the status would be `0` if `CORS check` fails for the cross origin resource would suffice, but it seems I'm missing something.

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

Message ID: <whatwg/fetch/pull/1468/review/1052690008@github.com>