DevTools: instrument network events from the browser process |
|||
Issue descriptionWe plan to move DevTools network instrumentation to the browser process and perform it from DevToolsURLLoaderInterceptor. This will allow: - merge interception and instrumentation ids (and, possible, protocol events) - stop routing sensitive data (e.g. HTTP-only cookies) through renderer; - unify navigation and sub-resource instrumentation. More details here: https://docs.google.com/document/d/1D_1EktSKNzxLD2MK36LQZdqI0n45G-KxPebUmn-wdMo/#heading=h.th00aosfn1l8
,
Jun 5 2018
Thanks! This sounds like it will resolve one of the known issues for Site Isolation, which is that DevTools doesn't show cookies or other headers on cross-site subresources (after issue 793692 ). https://www.chromium.org/Home/chromium-security/site-isolation#TOC-Known-Issues It will also probably offer a better solution for issue 834771 (where we're allowing some security connection data into untrusted renderers to get the security panel to work). I think you mentioned offline that this work might be dependent on the network service?
,
Nov 9
|
|||
►
Sign in to add a comment |
|||
Comment 1 by caseq@chromium.org
, Jun 5 2018