The chrome network debugger gives me a great view of all the HTTP resources loaded for a page. But it clears the list whenever a new top-level HTML page is loaded. This makes it very difficult to debug pages that automatically reload for one reason or another (running script or 300 responses).

Can I tell chrome not to clear the Network debugger when a new top-level page is loaded? Or can I go back and look at the previous page’s network resources?

Or can I somehow force chrome to pause before loading a new page when I don’t control the page I’m trying to debug that’s doing the redirecting? It’s part of an openid dance that’s going awry, so the combination of SSL and credentials makes it extremely difficult to debug with command-line tools.

Schreibe einen Kommentar