Run all existing tests with OOR-CORS and Servicified Service Worker enabled,
https://chromium-review.googlesource.com/c/chromium/src/+/1163547,
and classify failure cases.
https://docs.google.com/document/d/1H6K5zjosoVWjQunO1tDSAzv6dlu5Vg0hJ3fZQua2_d0/edit?usp=sharing
All failed tests can be roughly classified into following cases. First two cases are majority.
- CORS requests from Chrome Extensions are blocked unexpectedly
- Polymer load fails and can not start testing (html import related?)
- File access is blocked unexpectedly
- CORS requests from PPAPI are blocked unexpectedly
- Unknown timeout (needs further investigation)
- CORS related flag does not work
+ CORS disabler (--disable-web-sercurity)
+ File access enabler (--allow-file-access)
- CHECK failures
+ in CORSURLLoader redirect logic
+ IO thread check
- RANGE header is not permitted by CORS
- Save-Data header disappears in SW
- Different net error (ERR_ABORTED vs ERR_FAILED)
- unexpected network request completion
- failures due to Servicified Service Worker (we'll ignore them at this moment)
Comment 1 by toyoshim@chromium.org
, Aug 7Status: Duplicate (was: Available)