How to use Chrome's network debugger with redirects

http google-chrome google-chrome-devtools

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.

How did this duplicate get more upvotes than the one posted 1 month before it? stackoverflow.com/q/10703944/632951

@Pacerier The one you linked doesn't appear to be posted by you, but the reasoning is likely that it doesn't have "Chrome" in the title. When people are looking for something related to Chrome their search usually includes the keyword Chrome. "Google Developer Tools" is incredibly ambiguous.

gist.github.com/InstanceOfMichael/f6a509b84fe82a718816

bfncs

This has been changed since v32, thanks to @Daniel Alexiuc & @Thanatos for their comments.

Current (≥ v32)

At the top of the "Network" tab of DevTools, there's a checkbox to switch on the "Preserve log" functionality. If it is checked, the network log is preserved on page load.

https://i.stack.imgur.com/cFuNP.png

The little red dot on the left now has the purpose to switch network logging on and off completely.

Older versions

In older versions of Chrome (v21 here), there's a little, clickable red dot in the footer of the "Network" tab.

https://i.stack.imgur.com/tSUP0.png

If you hover over it, it will tell you, that it will "Preserve Log Upon Navigation" when it is activated. It holds the promise.

In version 32 it's still there, but has moved to the top of the network panel.

Actually, it's now at the top, but called "Preserve log", and is a checkbox. Confusingly, there's still a red record icon, but that's just whether to log at all.

Thanks for commenting on the change, I just updated the answer accordingly.

@ruben, the interface does indeed now look a bit different, but there's still a checkbox labeled "Preserve log" at the top of the network tab: i.imgur.com/fhSDYSz.png

@rubenlop88 Make sure you're not filtering on Documents, otherwise they won't persist there. You can check them specifically in the Other tab.

Matt York

I don't know of a way to force Chrome to not clear the Network debugger, but this might accomplish what you're looking for:

Open the js console window.addEventListener("beforeunload", function() { debugger; }, false)

This will pause chrome before loading the new page by hitting a breakpoint.

This wasn't the right answer for the question, but it's actually what I'm looking for. Thanks.

This is so slick. I got here looking for a "pause before redirect" solution and here it is. The accepted answer is easier to remember but this is rad.

This is extremely useful, because chrome does not shows the server response body, if the browser redirects right after getting the response.

Ofir Hadad

Another great solution to debug the Network calls before redirecting to other pages is to select the beforeunload event break point

This way you assure to break the flow right before it redirecting it to another page, this way all network calls, network data and console logs are still there.

This solution is best when you want to check what is the response of the calls

https://i.stack.imgur.com/OxHxo.png

https://i.stack.imgur.com/CNGXB.png

This is great. With the load event, we can stop at the beginning and set break point easily. Thanks!

This doesn't work for me just by ticking the checkbox. The javascript snippet window.addEventListener("beforeunload", function() { debugger; }, false) is necessary.

No, it's not. I'm using it daily.

"This solution is best when you want to check what is the response of the calls" Preserving not just the request data while being redirected from one site to another, but also the response data is exactly what I need. Four years have past since your post and a seemingly obvious feature such as having the network trace capture and keep the raw response data still isn't supported?

s-f

Just update of @bfncs answer

I think around Chrome 43 the behavior was changed a little. You still need to enable Preserve log to see, but now redirect shown under Other tab, when loaded document is shown under Doc.

This always confuse me, because I have a lot of networks requests and filter it by type XHR, Doc, JS etc. But in case of redirect the Doc tab is empty, so I have to guess.

How to use Chrome's network debugger with redirects

Follow WeChat

Want to stay one step ahead of the latest teleworks?

相似问题

Platform

Support

Links

Contact US