Google Git
Sign in
chromium / chromium / src / b3a0ac472cd61dcfede159fc0a85f551e9ca325a
commitb3a0ac472cd61dcfede159fc0a85f551e9ca325a[log] [tgz]
authorKenichi Ishibashi <bashi@chromium.org>Mon Mar 24 08:13:15 2025
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Mar 24 08:13:15 2025
treefe38dd74f25c2a9bc342d944f2419330b22d9006
parent48cca0143963e8826bfc907d6281969262c99f1a [diff]
Support dynamic update of the HappyEyeballsV3 feature

crrev.com/c/6332599 introduced a startup parameter to enable/disable
the feature. The plan was to set the parameter based on an enterprise
policy when initializing the NetworkService using
ContentBrowserClient, but the plan didn't work well for all platforms.
For example, initializing the NetworkService may happen on non-UI
threads while the UI thread can only access the PrefService.

This CL removes the startup parameter. Instead, this CL adds dynamic
update via ConfigureStubHostResolver() as suggested initially [1].
Updating the feature flag requires closing existing connections
since the feature controls how the network service establishes
connections. To support dynamic update, HttpNetworkSession always
initializes HttpStreamPool.

This CL doesn't add an enterprise policy yet. A subsequent CL will
add the policy.

[1] https://chromium-review.googlesource.com/c/chromium/src/+/6332599/comment/4bb5c458_3aa1cb7a/

Bug: 401410305
Change-Id: I8fb10e002c8be60dc95e0f7305cf8939f56c7115
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6381614
Commit-Queue: Kenichi Ishibashi <bashi@chromium.org>
Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org>
Reviewed-by: Rakina Zata Amni <rakina@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1436711}
12 files changed
tree: fe38dd74f25c2a9bc342d944f2419330b22d9006
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. crypto/
  16. dbus/
  17. device/
  18. docs/
  19. extensions/
  20. fuchsia_web/
  21. gin/
  22. google_apis/
  23. gpu/
  24. headless/
  25. infra/
  26. ios/
  27. ipc/
  28. media/
  29. mojo/
  30. native_client_sdk/
  31. net/
  32. pdf/
  33. ppapi/
  34. printing/
  35. remoting/
  36. rlz/
  37. sandbox/
  38. services/
  39. skia/
  40. sql/
  41. storage/
  42. styleguide/
  43. testing/
  44. third_party/
  45. tools/
  46. ui/
  47. url/
  48. webkit/
  49. clank
  50. internal
  51. ios_internal
  52. native_client
  53. signing_keys
  54. v8
  55. .clang-format
  56. .clang-tidy
  57. .clangd
  58. .git-blame-ignore-revs
  59. .gitallowed
  60. .gitattributes
  61. .gitignore
  62. .gitmodules
  63. .gn
  64. .mailmap
  65. .rustfmt.toml
  66. .vpython3
  67. .yapfignore
  68. ATL_OWNERS
  69. AUTHORS
  70. BUILD.gn
  71. CODE_OF_CONDUCT.md
  72. codereview.settings
  73. CPPLINT.cfg
  74. CRYPTO_OWNERS
  75. DEPS
  76. DIR_METADATA
  77. LICENSE
  78. LICENSE.chromium_os
  79. OWNERS
  80. PRESUBMIT.py
  81. PRESUBMIT_test.py
  82. PRESUBMIT_test_mocks.py
  83. README.md
  84. 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.