Fetch: Access-Control-Expose-Headers: * #5047
Conversation
Belated test for whatwg/fetch#252.
|
Notifying @jdm and @youennf. (Learn how reviewing works.) |
|
These tests are now available on w3c-test.org |
Firefox (nightly channel)Testing web-platform-tests at revision 06e4d7b All results2 tests ran/fetch/api/cors/cors-expose-star-worker.html
/fetch/api/cors/cors-expose-star.html
|
Chrome (unstable channel)Testing web-platform-tests at revision 06e4d7b All results2 tests ran/fetch/api/cors/cors-expose-star-worker.html
/fetch/api/cors/cors-expose-star.html
|
| const url = "http://{{host}}:{{ports[http][1]}}" + dirname(location.pathname) + RESOURCES_DIR + "top.txt", | ||
| sharedHeaders = "?pipe=header(Access-Control-Expose-Headers,*)|header(Test,X)|header(Set-Cookie,X)|" | ||
|
|
||
| promise_test(() => { |
There was a problem hiding this comment.
Having looked for and not found the use of the argument, I removed it.
There was a problem hiding this comment.
Thanks for filing the impl bugs, there was some discussion on whatwg/fetch#252 but let's see if any more concerns appear. Until then, the tests LGTM.
| assert_equals(resp.headers.get("test"), null) | ||
| assert_equals(resp.headers.get("set-cookie"), null) | ||
| }) | ||
| }, "Cannot use * for credentialed fetches") |
There was a problem hiding this comment.
Good, this also gives me some confidence that the above test will pass if the feature is implemented 👍
Belated test for whatwg/fetch#252.