Bug 169550
| Summary: | CORS: 100/101 do not cause rejection of CORS preflight | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Anne van Kesteren <annevk> |
| Component: | DOM | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED CONFIGURATION CHANGED | ||
| Severity: | Normal | CC: | ahmad.saleem792, ap, cdumez, rniwa, youennf |
| Priority: | P2 | ||
| Version: | Safari Technology Preview | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Anne van Kesteren
web-platform-tests:
cors/preflight-failure.htm
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
Where can this test be found?
youenn fablet
See https://github.com/w3c/web-platform-tests/tree/master/cors.
We should import that test suite.
Ahmad Saleem
We pass all tests on WPT (Safari Technology Preview 166):
https://wpt.fyi/results/cors/preflight-failure.htm?label=master&label=experimental&aligned=&q=preflight-failure.htm
Can we close this now?
Anne van Kesteren
We should probably still synchronize the test suite again. But that is in part blocked on making multiple hosts work better in the test infrastructure.
Anne van Kesteren
On reflection we probably don't need a separate tracking bug for just that. Once that larger bug is fixed these test suites will get resynchronized for sure.