commit | f48bd25089e7fd7f988f98456ae1dd5a183a2a5c | [log] [tgz] |
---|---|---|
author | Tsuyoshi Horo <horo@chromium.org> | Tue Apr 15 01:15:21 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Apr 15 01:15:21 2025 |
tree | 6a33644a54d27b9de69e4e772ea7343ac8f86769 | |
parent | 6ffd8e08bbf598c726987e878cb5d0d85f92cae6 [diff] |
network: Refactor URLLoader::BuildResponseHead into url_loader_util Extract the logic for constructing mojom::URLResponseHead from URLLoader::BuildResponseHead into a new utility function network::url_loader_util::BuildResponseHead. This refactoring aims to: - Decouple the response head construction logic from the URLLoader class. - Improve maintainability by placing the construction logic in a dedicated utility file. The new function takes the necessary data (URLRequest, parsed request cookies, PNA address spaces, load options, etc.) as parameters. The URLLoader method now simply gathers these parameters from its member variables and state, and calls the utility function. An explicit CHECK is added in URLLoader before calling the utility function to ensure consistency regarding `request_cookies_` and the `include_request_cookies_with_response_` option, which was previously handled within the original method. No behavior change is intended by this refactoring. Bug: 408106280 Change-Id: Ib970ad0b5a23a2d5e790164e80ef3179fb048989 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6450656 Reviewed-by: Kenichi Ishibashi <bashi@chromium.org> Commit-Queue: Tsuyoshi Horo <horo@chromium.org> Commit-Queue: Kenichi Ishibashi <bashi@chromium.org> Reviewed-by: Adam Rice <ricea@chromium.org> Cr-Commit-Position: refs/heads/main@{#1446886}
Chromium 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.