Findings from net::URLRequestContext audit

[Helen Li]

Early last week, I did an exercise (837333) to see if there are use cases of net::URLRequestContext that network service needs and that aren't tracked.

Tl;dr: see this internal doc for remaining tasks.

- Most are already being tracked in the list (that mmenke@ started and we have been adding more to). These fall into few buckets: Configuration options, Certs, SSL, Cache, NetLog, DNS, Proxies, HttpAuth, RDH/legacy loading path, and others.

- Most StoragePartition::GetURLRequestContext()s are for net::URLFetcher APIs. It's being worked on in 773295.

- Found a few untracked use cases, but otherwise uneventful. (e.g. 838949 chrome.benchmarking injects JavaScript APIs to clear networking data; 838964 data that needs to exposed to the UI). I've added them to the list and on the bug tracker.

- Removed a few stale references and hid legacy APIs like URLRequestContextGetterObserver.

[John Abd-El-Malek]

Thanks Helen for the good news :)

--
You received this message because you are subscribed to the Google Groups "network-service-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to network-service-dev+unsub...@chromium.org.
To post to this group, send email to network-service-dev@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/network-service-dev/CAEkFr04baC%2BF%3D-rs3F%3DLG3XupaoYo3ShHda3O4txhO5YbTcfbg%40mail.gmail.com.