Use base::Time::FromUTCString() in ParseDate()

This switches from ParseDateFromNullTerminatedCharacters() to the
base::Time equivalent in ParseDate().

Based on data collected by the use counters:

 https://chromestatus.com/metrics/feature/timeline/popularity/5128 and
 https://chromestatus.com/metrics/feature/timeline/popularity/5129

there are some differences. The relevant cases in which the parsers
differ has been identified as:

1) Unrecognized timezone labels. For example KST, MSK, EEST, YEKT and
   BST.

2) The base::Time parser accepts trailing garbage, like:

    * "Mon, 02 Jun 2025 11:55:15 CEST (cached)",
    * "Mon, 02 Jun 2025 10:04:55 GMT, Mon, 02 Jun 2025 10:04:55 GMT" and
    * "Mon, 02 Jun 2025 10:06:26 GMT GMT"

3) The base::Time parser accepts a timezone offset before the timezone
   label or without a separating space, like:

    * "Sat, 24 May 2025 11:13:11 +0300 GMT" and
    * "2025-06-01T21:07:14-03:00"

4) The ParseDateFromNullTerminatedCharacters() produce incorrect
   date/time for dates that are in the future, like:

    * "Wed, 11 Apr 2035 09:34:46 GMT" (wrong day)
    * "Wed, 08 Nov 2051 17:56:46 GMT" (wrong day)
    * "Tue, 19 Jan 2038 03:14:07 GMT" (wrong day)
    * "Mon, 31 Dec 2040 00:00:00 GMT" (wrong day)
    * "Tue, 19 Jan 2038 03:14:07 GMT" (wrong day)
    * "Sun, 05 Dec 2032 16:06:02 +0000" (wrong hour)

Bullet point (4) should be enough motivation to switch. In all cases,
the base::Time parser is more correct or accepting.

Guarded by flag "ParseDateUsesBaseTimeFromUtcString".

Bug: 375343405
Change-Id: Ic75ced160773b8c6b7db0444cc20c1e5c3c399cc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6611178
Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/main@{#1468635}
2 files changed
tree: bf38954dee1071bb8fc4c919577ff37efb539af4
  1. .github/
  2. android_webview/
  3. apps/
  4. ash/
  5. base/
  6. build/
  7. build_overrides/
  8. buildtools/
  9. cc/
  10. chrome/
  11. chromecast/
  12. chromeos/
  13. codelabs/
  14. components/
  15. content/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. gpu/
  25. headless/
  26. infra/
  27. ios/
  28. ipc/
  29. media/
  30. mojo/
  31. native_client_sdk/
  32. net/
  33. pdf/
  34. ppapi/
  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. .clang-format
  51. .clang-tidy
  52. .clangd
  53. .git-blame-ignore-revs
  54. .gitallowed
  55. .gitattributes
  56. .gitignore
  57. .gitmodules
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython3
  62. .yapfignore
  63. ATL_OWNERS
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. CPPLINT.cfg
  69. CRYPTO_OWNERS
  70. DEPS
  71. DIR_METADATA
  72. LICENSE
  73. LICENSE.chromium_os
  74. OWNERS
  75. PRESUBMIT.py
  76. PRESUBMIT_test.py
  77. PRESUBMIT_test_mocks.py
  78. README.md
  79. SECURITY_OWNERS
  80. 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.