Google Git
Sign in
chromium / chromium / src / b51fedb497b1a10dac3fb0d973bac748b846287e
commitb51fedb497b1a10dac3fb0d973bac748b846287e[log] [tgz]
authorEric Orth <ericorth@chromium.org>Wed Apr 16 23:52:42 2025
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Apr 16 23:52:42 2025
tree3f8f811ffe992ababe5ac014ba936480398c91c4
parent0d02261e1f9449c80d02c720527df2aaea4d2c14 [diff]
Allow IPv6 Hosts file resolution when IPv6 unreachable

Prior to crrev.com/c/6297626, when IPv6 is unreachable, Hosts file
resolution could still resolve IPv6 results as long as there are no
IPv4 results for the name or the only IPv4 results are loopback. After
the CL, the special case would only work when there is at least one
IPv4 loopback.

Fix to allow the no-IPv4 case again.

Noteworthy that system and built-in resolution have long differed in
this logic in that system resolution seems to have always required at
least one IPv4 loopback to allow the IPv6 resolution, and we therefore
accidentally made the logic more consistent. But the inconsistent
behavior has been in place for so long that we should go back to that
behavior without a deliberate effort to change things.

Bug: 410059466
Change-Id: I16071a3b19a101c570535a6d2f4ef14328f5f629
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6462046
Reviewed-by: Kenichi Ishibashi <bashi@chromium.org>
Commit-Queue: Eric Orth <ericorth@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1448081}
2 files changed
tree: 3f8f811ffe992ababe5ac014ba936480398c91c4
  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.