Bug 169194 - [Fetch API] implement Access-Control-Expose-Headers: *
Summary: [Fetch API] implement Access-Control-Expose-Headers: *
Status: RESOLVED DUPLICATE of bug 165508
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: Safari Technology Preview
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: youenn fablet
Depends on:
Reported: 2017-03-06 04:30 PST by Anne van Kesteren
Modified: 2019-08-20 02:31 PDT (History)
8 users (show)

See Also:

Patch (12.58 KB, patch)
2017-03-21 13:16 PDT, youenn fablet
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Anne van Kesteren 2017-03-06 04:30:05 PST
Tests: https://github.com/w3c/web-platform-tests/pull/5047.

Note that this isn't specific to the Fetch API, it also applies to, e.g., XMLHttpRequest, but this label seemed closest to what was already in use.
Comment 1 Anne van Kesteren 2017-03-08 02:18:24 PST
Tests for Access-Control-Allow-Methods/Headers: * at https://github.com/w3c/web-platform-tests/pull/5050. Let me know if you need a separate issue.
Comment 2 youenn fablet 2017-03-21 13:16:05 PDT
Created attachment 305018 [details]
Comment 3 youenn fablet 2017-03-21 21:25:04 PDT
Submitted web-platform-tests pull request: https://api.github.com/repos/w3c/web-platform-tests/issues/5190
Comment 4 youenn fablet 2017-03-21 21:47:11 PDT
Submitted web-platform-tests pull request: https://github.com/w3c/web-platform-tests/pull/5191
Comment 5 Anne van Kesteren 2017-09-01 05:16:56 PDT
FYI: we're changing the behavior slightly here: https://github.com/whatwg/fetch/pull/592.
Comment 6 Anne van Kesteren 2017-09-07 01:57:50 PDT
Behavior changed, updated tests at https://github.com/w3c/web-platform-tests/pull/7223. No outstanding issues now.
Comment 7 shacharz 2018-12-06 07:19:47 PST
Any update?
Comment 8 Rob Buis 2019-06-15 04:39:57 PDT
I think this is fixed by:
Also the WPT test got imported here:
Comment 9 youenn fablet 2019-08-20 02:31:38 PDT

*** This bug has been marked as a duplicate of bug 165508 ***