Reporting (from the renderer) fails when NetworkService is enabled |
|||||||
Issue descriptionWhen the renderer generates a deprecation or intervention report, it uses mojom::ReportingServiceProxy to queue it to the reporting service. The receiving end looks to be running in the browser process as content::ReportingServiceProxyImpl (content/browser/net/), and tries to forward it to the reporting service hanging off the URLRequestContext. Which will presumably be missing when NetworkService is enabled: https://chromium.googlesource.com/chromium/src/+/HEAD/content/browser/net/reporting_service_proxy.cc#132
,
Nov 13
Sure I can take this! As you pointed out, it shouldn't be a big change.
,
Nov 14
Thanks
,
Nov 26
,
Nov 27
,
Nov 27
,
Nov 27
,
Nov 29
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/218c5ce59314b0d17c45c37207640af0975ea3ba commit 218c5ce59314b0d17c45c37207640af0975ea3ba Author: Eric Roman <eroman@chromium.org> Date: Thu Nov 29 18:03:13 2018 Use NetworkContext to queue reports. Bug: 903948 Change-Id: Ida8e955b212f26c9938a43cb196d9f90aac3404b Reviewed-on: https://chromium-review.googlesource.com/c/1351098 Commit-Queue: John Abd-El-Malek <jam@chromium.org> Reviewed-by: John Abd-El-Malek <jam@chromium.org> Cr-Commit-Position: refs/heads/master@{#612271} [modify] https://crrev.com/218c5ce59314b0d17c45c37207640af0975ea3ba/content/browser/net/reporting_service_proxy.cc [modify] https://crrev.com/218c5ce59314b0d17c45c37207640af0975ea3ba/content/browser/net/reporting_service_proxy.h [modify] https://crrev.com/218c5ce59314b0d17c45c37207640af0975ea3ba/content/browser/renderer_host/render_process_host_impl.cc
,
Nov 29
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by jam@chromium.org
, Nov 13