Google Git
Sign in
chromium / chromium / src / ee9e4b7dbb33a548fa1cc97e734e4bda272b5c3f
commitee9e4b7dbb33a548fa1cc97e734e4bda272b5c3f[log] [tgz]
authorTakashi Nakayama <tnak@chromium.org>Tue Sep 02 16:16:05 2025
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Sep 02 16:16:05 2025
tree2c26ad8a0626fe7381acda6c34aa0d7064965a86
parent53b3687eef8b4e8137f58c68e6d9f53e758b8b4a [diff]
Preloading: Plumb per URL UserAgentOverrideOption for Prerender2

Currently, //content preloading (unified prefetch cache) does not
support WebContents-level User-Agent and Ch-Ua header overrides. This CL
is the first step to implement this feature by adding a logic to plumb
UserAgentOverrideOption, core data to decide if applying UA overrides or
not, by:

1. Enable per URL decisions by adding an argument to
`ShouldOverrideUserAgentForPrerender2()`.

2. Calling the Clank side, source of truth logic in
`WebContentsDelegateAndroid`.

The new feature flag `PreloadingRespectUserAgentOverride` is introduced
by this CL. All upcoming changes will be behind this flag, and this flag
will be enabled by default after whole fix are implemented.

See the investigation doc [1] for the details of UA override data types.

[1] https://docs.google.com/document/d/14gzNT-AGhZLHEJXbxra2cIgUnyagdIC2Q3vzJycqZ2c/edit?usp=drivesdk

Bug: 441612842
Change-Id: I7c932b62c8feb42f013e2781dff26ed98a9ed383
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6893774
Commit-Queue: Takashi Nakayama <tnak@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Reviewed-by: Peter Conn <peconn@chromium.org>
Reviewed-by: Jinsuk Kim <jinsukkim@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1509612}
12 files changed
tree: 2c26ad8a0626fe7381acda6c34aa0d7064965a86
  1. .gemini/
  2. .github/
  3. agents/
  4. android_webview/
  5. apps/
  6. ash/
  7. base/
  8. build/
  9. build_overrides/
  10. buildtools/
  11. cc/
  12. chrome/
  13. chromecast/
  14. chromeos/
  15. codelabs/
  16. components/
  17. content/
  18. crypto/
  19. dbus/
  20. device/
  21. docs/
  22. extensions/
  23. fuchsia_web/
  24. gin/
  25. google_apis/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. media/
  32. mojo/
  33. net/
  34. pdf/
  35. printing/
  36. remoting/
  37. rlz/
  38. sandbox/
  39. services/
  40. skia/
  41. sql/
  42. storage/
  43. styleguide/
  44. testing/
  45. third_party/
  46. tools/
  47. ui/
  48. url/
  49. webkit/
  50. clank
  51. clusterfuzz-data
  52. internal
  53. ios_internal
  54. signing_keys
  55. v8
  56. .clang-format
  57. .clang-tidy
  58. .clangd
  59. .cursorignore
  60. .geminiignore
  61. .git-blame-ignore-revs
  62. .gitallowed
  63. .gitattributes
  64. .gitignore
  65. .gitmodules
  66. .gn
  67. .mailmap
  68. .rustfmt.toml
  69. .vpython3
  70. .yapfignore
  71. ATL_OWNERS
  72. AUTHORS
  73. BUILD.gn
  74. CODE_OF_CONDUCT.md
  75. codereview.settings
  76. CPPLINT.cfg
  77. CRYPTO_OWNERS
  78. DEPS
  79. DIR_METADATA
  80. LICENSE
  81. LICENSE.chromium_os
  82. OWNERS
  83. PRESUBMIT.py
  84. PRESUBMIT_test.py
  85. PRESUBMIT_test_mocks.py
  86. README.md
  87. SECURITY_OWNERS
  88. WATCHLISTS
README.md

Logo Chromium

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.