Automatic update from web-platform-testsMove core CORB logic into //services/network.
This CL moves the core CORB logic (figuring out if a given response
should be CORB-protected based on 1) response metadata like initiator,
MIME type, CORS headers and 2) sniffing the first bytes of the response)
from //content/common into //services/network.
As part of the move, this CL makes some extra, opportunistic changes:
- Renames the moved files (and the moved class) to match the name agreed
upon in the explainer
(s/CrossSiteDocumentClassifier/CrossOriginReadBlocking)
- Also moves the explainer doc to //services/network
- Tweaks the old CrossSiteDocumentMimeType enum so that
- It is nested in CrossOriginReadBlocking::MimeType
- The enum values have shorter names
In the long-term, the core CORB logic should only be needed within
services/network. In the short-term, this logic has the following
consumers:
- content/browser/loader/cross_site_document_resource_handler.cc
(integrates CORB into the old, pre-network-service,
ResourceHandler-based world; this can go away after the network
service ships)
- content/renderer/loader/site_isolation_stats_gatherer.cc
(gathers UMA that help decide what responses can be blocked
by CORB with acceptably low risk of breaking existing websites;
this can go away after CORB ships)
- WIP(https://crbug.com/792546): services/network/url_loader.cc
(this will integrate CORB into the new, network-service world).
Bug: 792546
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: Ib8fe412b1f807d23e41700b7f7090cd4b77c1783
Reviewed-on: https://chromium-review.googlesource.com/929446
Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Nick Carter <nick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541661}
wpt-commits: 6cd55d2d27fa20b5c0f7d31e6899206eff44870b
wpt-pr: 9635
wpt-commits: 6cd55d2d27fa20b5c0f7d31e6899206eff44870b
wpt-pr: 9635
2203553a83