[whatwg/fetch] Use internal response for Server-Timing (PR #1584)

The `Server-Timing` header is protected by TAO, so there's no need to safelist it in CORS as well.

Closes #1511

<!--
Thank you for contributing to the Fetch Standard! Please describe the change you are making and complete the checklist below if your change is not editorial.
-->

- [ ] At least two implementers are interested (and none opposed):
   * Already implemented
- [ ] [Tests](https://github.com/web-platform-tests/wpt) are written and can be reviewed and commented upon at:
   * https://github.com/web-platform-tests/wpt/pull/37714

- [ ] [Implementation bugs](https://github.com/whatwg/meta/blob/main/MAINTAINERS.md#handling-pull-requests) are filed:
   * Already implemented
- [ ] [MDN issue](https://github.com/whatwg/meta/blob/main/MAINTAINERS.md#handling-pull-requests) is filed: …

(See [WHATWG Working Mode: Changes](https://whatwg.org/working-mode#changes) for more details.)

You can view, comment on, or merge this pull request online at:

  https://github.com/whatwg/fetch/pull/1584


-- Commit Summary --

  * Use internal response for Server-Timing

-- File Changes --

    M fetch.bs (6)

-- Patch Links --

https://github.com/whatwg/fetch/pull/1584.patch

https://github.com/whatwg/fetch/pull/1584.diff


-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/1584

You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/pull/1584@github.com>