[network] Export sanitized HARs by default.

This CL introduces a new disabled-by-default setting "Allow to generate
HAR (with sensitive data)", which guards the availability of options to
export/copy HARs with Cookie, Set-Cookie, and Authorization headers. By
default the exported/copied HARs will be sanitized to not include cookie
or authorization information.

This is reflected by renaming the titles of the actions accordingly to
"Copy all as HAR (sanitized)" and "Export HAR (sanitized)". Only when
the new setting is explicitly enabled by the user, a second set of
options becomes available, which allows to "Copy all as HAR (with
sensitive data)" and "Export HAR (with sensitive data)".

Please refer to the design document for further details and screenshots.

Doc: https://goo.gle/devtools-har-exclude-cookies-design
Bug: 361717594
Change-Id: I989175eec061c2f58bbd734a2f9e58a7b727bdba
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5846648
Reviewed-by: Danil Somsikov <dsv@chromium.org>
Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
Auto-Submit: Benedikt Meurer <bmeurer@chromium.org>
6 files changed
tree: 321d570cf6187c94ec664d10ee6f91d007cf8bea
  1. .vscode/
  2. build_overrides/
  3. config/
  4. docs/
  5. extension-api/
  6. extensions/
  7. front_end/
  8. inspector_overlay/
  9. node_modules/
  10. scripts/
  11. test/
  12. third_party/
  13. v8/
  14. .clang-format
  15. .editorconfig
  16. .eslintignore
  17. .eslintrc.js
  18. .git-blame-ignore-revs
  19. .gitallowed
  20. .gitattributes
  21. .gitignore
  22. .gitmodules
  23. .gn
  24. .mailmap
  25. .npmignore
  26. .npmrc
  27. .style.yapf
  28. .stylelintignore
  29. .stylelintrc.json
  30. AUTHORS
  31. BUILD.gn
  32. codereview.settings
  33. CONTRIBUTING.md
  34. DEPS
  35. favicon.ico
  36. LICENSE
  37. OWNERS
  38. package-lock.json
  39. package.json
  40. PRESUBMIT.py
  41. README.md
  42. tsconfig.json
  43. WATCHLISTS
README.md

Chrome DevTools frontend

npm package

The client-side of the Chrome DevTools, including all TypeScript & CSS to run the DevTools webapp.

Source code and documentation

The frontend is available on chromium.googlesource.com. Check out the Chromium DevTools documentation for instructions to set up, use, and maintain a DevTools front-end checkout, as well as design guidelines, and architectural documentation.

Source mirrors

DevTools frontend repository is mirrored on GitHub.

DevTools frontend is also available on NPM as the chrome-devtools-frontend package. It's not currently available via CJS or ES modules, so consuming this package in other tools may require some effort.

The version number of the npm package (e.g. 1.0.373466) refers to the Chromium commit position of latest frontend git commit. It's incremented with every Chromium commit, however the package is updated roughly daily.

Getting in touch

There are a few options to keep an eye on the latest and greatest of DevTools development: