Google Git
Sign in
chromium / chromium / src / 5d890e528d08c317d73b4ecd02c21e12fd648694
commit5d890e528d08c317d73b4ecd02c21e12fd648694[log] [tgz]
authorRakina Zata Amni <rakina@chromium.org>Tue Apr 02 05:01:16 2024
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Apr 02 05:01:16 2024
treeae31822978394b774dbd8c72278f4e946ca7e63a
parenteb7475582501e654b3c0bb94be9fdbadfd6b83a0 [diff]
Add precursor origin to data: URL worker's new opaque origin

Data: URL workers will create a new opaque origin to be used on
the renderer side, completely unrelated to the starter/creator
origin. However, currently the origin on the browser side
WorkerHost object will inherit the origin of the creator instead
(see linked bug for details). This difference makes it hard for
the browser side to do comparisons with the renderer origin, e.g.
for Blob URL origin validation and calculation mentioned in
https://docs.google.com/document/d/11W23BkCnccyPtZD6_DKeokL8ROxWBQQl2Rn5_GdAYOU/edit#bookmark=id.dmysys1y3kk9.

To make it easier for the browser side to validate renderer-side
origin of data: URL workers and the Blob URLs they create, add
the creator origin as a precursor origin to the new opaque
origin used by those workers on the renderer side. We can use
the precursor to compare with the origin used on the browser
side, like we do in crrev.com/c/5401110.

Bug: 1058759
Change-Id: Ib6ce1138bd77425975bcb8114cb647c2f841ecb1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5401139
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Commit-Queue: Rakina Zata Amni <rakina@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1281012}
1 file changed
tree: ae31822978394b774dbd8c72278f4e946ca7e63a
  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. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. webkit/
  51. clank
  52. internal
  53. ios_internal
  54. native_client
  55. signing_keys
  56. v8
  57. .clang-format
  58. .clang-tidy
  59. .clangd
  60. .eslintrc.js
  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. DEPS
  77. DIR_METADATA
  78. LICENSE
  79. LICENSE.chromium_os
  80. OWNERS
  81. PRESUBMIT.py
  82. PRESUBMIT_test.py
  83. PRESUBMIT_test_mocks.py
  84. README.md
  85. 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.