DCHECK that a committing frame receives valid URLLoaderFactory bundle.

The primary goal of this CL, is being able to add the following DCHECKs:
    DCHECK(loader_factories_);
    DCHECK(loader_factories_->HasBoundDefaultFactory());
to RenderFrameImpl::DidCommitNavigation.  If these DCHECKs hold, then
ChildURLLoaderFactoryBundle::GetFactory should always get the
|base_result| from the base class and therefore shouldn't ever need to
fall back ot the |direct_network_factory_| fallback (which wraps the
deprecated, process-wide / frame-agnostic factory).

One scenario where the new DCHECKs didn't hold before this CL is
RenderFrameImpl::LoadHTMLString which is mostly used from tests, but
also has a call in the product from
MimeHandlerViewContainerManager::LoadEmptyPage which is used by
MimeHandlerViewEmbedder::CheckSandboxFlags to load an empty page when
security checks fail.  Another scenario is unit tests like
RenderViewImplTest going through TestRenderFrame (where tests drive the
simulated commit).  All of these cases don't actually use the factory
bundle and therefore can just use the NotImplementedURLLoaderFactory.

The CL splits GetLoaderFactoryBundleFallback from
GetLoaderFactoryBundleFromCreator to make it more obvious when the
fallback is actually needed.  In particular, this allows the new DCHECKs
in RenderFrameImpl::DidCommitNavigation to explicitly avoid the
fallback.

To facilitate reuse of NotImplementedURLLoaderFactory from
//content/renderer the CL moves this class from //content/test into
//services/network/public/cpp.  The CL also adds NOTREACHED to
NotImplementedURLLoaderFactory::CreateLoaderAndStart to ensure that
future callers don't accidentally start using the factory.

NOTREACHED is also added to the non-opaque-origin/DwoC case in
ChildURLLoaderFactoryBundle::GetFactory (this probably should have been
part of r792963 which added a test that would have hit this NOTREACHED
before the fix).

Bug: 1098938, 1105794
Change-Id: Ifaedf40be35871b0a30797c09a236ea131b24447
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2321346
Reviewed-by: Kinuko Yasuda <[email protected]>
Commit-Queue: Ɓukasz Anforowicz <[email protected]>
Cr-Commit-Position: refs/heads/master@{#794566}
12 files changed
tree: 4118deb3a6159d61aa557741d8a5938670a54042
  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. cloud_print/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. jingle/
  31. media/
  32. mojo/
  33. native_client_sdk/
  34. net/
  35. pdf/
  36. ppapi/
  37. printing/
  38. remoting/
  39. rlz/
  40. sandbox/
  41. services/
  42. skia/
  43. sql/
  44. storage/
  45. styleguide/
  46. testing/
  47. third_party/
  48. tools/
  49. ui/
  50. url/
  51. weblayer/
  52. .clang-format
  53. .clang-tidy
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitattributes
  57. .gitignore
  58. .gn
  59. .vpython
  60. .vpython3
  61. .yapfignore
  62. AUTHORS
  63. BUILD.gn
  64. CODE_OF_CONDUCT.md
  65. codereview.settings
  66. DEPS
  67. DIR_METADATA
  68. ENG_REVIEW_OWNERS
  69. LICENSE
  70. LICENSE.chromium_os
  71. OWNERS
  72. PRESUBMIT.py
  73. PRESUBMIT_test.py
  74. PRESUBMIT_test_mocks.py
  75. README.md
  76. 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.

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.