fetch: Null body responses should fail subresource integrity check Step 22.2 of https://fetch.spec.whatwg.org/#concept-main-fetch says we should abort when integrity metadata exists but body is null. Bug: 1427319 Change-Id: Id8bbd5718e41e1d56b7b5f5c9b570921c86f12f1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4369159 Reviewed-by: Kentaro Hara <haraken@chromium.org> Reviewed-by: Adam Rice <ricea@chromium.org> Commit-Queue: Kenichi Ishibashi <bashi@chromium.org> Cr-Commit-Position: refs/heads/main@{#1121596}
ChromiumChromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.