about:net-internals is implemented in chrome/ layer rather then in content/ leads to different behavior in headless mode
Reported by
m...@louisroche.net,
Nov 6 2017
|
|||
Issue descriptionChrome Version : Chromium 64.0.3245.0 URLs (if applicable) : chrome://net-internals As reported on the puppeteer bugtracker, there is a different behavior when going to chrome://net-internals using headless mode and non headless mode. I'm not sure of what is exactly the problem, so I am quoting Andrey Lushnikov here: > It looks like about:net-internals is implemented in chrome/ layer rather then in content/. original issue: https://github.com/GoogleChrome/puppeteer/issues/1056
,
Nov 8 2017
Right, chrome://net-internals isn't supported in headless mode. Is there a reason you'd need it to work?
,
Nov 9 2017
I don't know of any other way to check what is happening on the network (events, timeline) or the configuration (proxy). Especially useful as headless doesn't support all the "normal" features yet (like the proxy-pac is missing). So it is convenient to have a point to check what is really happening.
,
Aug 3
I want chrome://net-internals in headless mode so that I can clear DNS cache and socket pools without requiring my users to do it manually. Is there a way to achieve both of those without access to chrome://net-internals? If I read correctly, I can modify the hosts file to clear chrome's DNS cache, but is there a way to clear its socket pool?
,
Aug 26
I'm using Puppeteer and trying to get HTTP_STREAM_JOB_CONTROLLER info. Still checking the documentation, but so far, can't get to it without chrome://net-internals. So, that is the reason -- for me, anyway. Maybe more of a Puppeteer issue, idk. P.S.: What is issue 705916? Doesn't seem to exist. |
|||
►
Sign in to add a comment |
|||
Comment 1 by ajha@chromium.org
, Nov 8 2017Labels: TE-NeedsTriageHelp