As we get closer to shipping the network service, we should restrict access to net/ APIs in Chrome and content/.
One way to do this would be to restrict access to in-process net objects in Chrome by making their methods private, and friending the current callers (Both legacy callers that need to be updated not to use the APIs, and consumers that can safely continue to use them, if any). This will both provide a list of consumers that need to be updated, and prevent new dependencies from slipping in unexpected.
The most obvious places this can get done are URLRequestContextGetter, IOThread, and (possibly) URLRequestContext itself - though URLRequestContext accessors will mostly be covered by addressing the first two, and tearing down content/browser/loader, and things that hook into it.
Comment 1 by xunji...@chromium.org
, Apr 27 2018Owner: xunji...@chromium.org
Status: Assigned (was: Untriaged)