Remove per-client CORS checks
Those are needed because a request could match with another request made by a foreign origin, but [1] fixed the issue. This is basically reverting [2]. Two layout tests are added to detect regressions. This CL changes the behavior a bit. Without this CL, - A response with a proper access-control-allow-origin header for a cross-origin request with "no-cors" mode is treated as non-opaque, and - A response without a proper access-control-allow-origin header for a same-origin request with "no-cors" mode redirected from a cross-origin resource is treated as opaque while with this CL, - A response with a proper access-control-allow-origin header for a cross-origin request with "no-cors" mode is treated as opaque, and - A response without a proper access-control-allow-origin header for a same-origin request with "no-cors" mode redirected from a cross-origin resource is treated as non-opaque. Also, before this CL, CORSStatus is calculated with an opaque origin for top-level worklet scripts. This CL changes that: now CORSStatus is calculated with the origin of the parent context, and so it stops muting error messages in worklets. 1: https://chromium.googlesource.com/chromium/src.git/+/c1df004861ab704945d31a0d207bb7f4c205e60c 2: https://chromium.googlesource.com/chromium/src.git/+/fad67a5b73639d7211b24fd9bdb242e82039b765 Bug: 809350, 799477 Change-Id: If28f59f6e6ac03a4d5992cca85801231748019bd Reviewed-on: https://chromium-review.googlesource.com/1158165 Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Reviewed-by:Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by:
Fredrik Söderquist <fs@opera.com> Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Reviewed-by:
Takashi Toyoshima <toyoshim@chromium.org> Cr-Commit-Position: refs/heads/master@{#583202}
Showing
Please register or sign in to comment