Re: [Chrome DevTools] XHR requests don't seem to be captured in Canary

[Vsevolod Vlasov]

XHRs could be served from cache and therefore not displayed in the network panel. Do you think this might be a case?

Could you check if the server actually receives a second request - if it does then this is a bug. In this case I would ask you to file a bug on http://crbug.com/new providing as much details as possible (repro URL etc.) and send a link to this bug here.

On Mon, Dec 2, 2013 at 2:39 PM, Adrien Giboire <adrien....@gmail.com> wrote:

Hi there!

First, I'm not sure if this is the right place to talk about Canary but I didn't find a better place right now.

So, I'm working on an Angular app. And requesting the same URL with Canary (33.0.1726.0 canary) does not show me all the XHR request. Only the first one. While Chrome (31.0.1650.57) does work well.

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/d860a781-dbff-4f0c-b055-0c0635866478%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[PhistucK]

Is this a new behavior (excluding cached XMLHttpRequests)?

Are regular resources that are loaded from cache also excluded?

If this is a new behavior and cached resources are also excluded, this sounds bad. Like excluding data URIs got reverted, this should get reverted, too. Actually, this sounds bad even if it is not a new behavior. The network panel, perhaps misnamed, should show any request or communication the browser makes for the page, including WebRTC information (currently not supported), cached requests, plugin sub resource requests (Flash, mostly, I guess), non web protocols (file://, or whatever://). This information is extremely helpful to the developer and can provide a lot of information regarding latency, page load times, race conditions and more that are crucial for debugging.

☆PhistucK

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/CAB6O%2BxY7RND3_avF44HwAbDfRB%2BmNtDZe03f8O83qMv9LWKsAw%40mail.gmail.com.

[Pavel Feldman]

What you are talking about is timeline. As for cached XHRs that are missing in network panel, please file a bug with the sample you have on mind.

Regards
Pavel

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/CABc02_Ksqq792Dp%2BJJZ46%3DQp3M_%2BWiEAvU8WmLkHCeAx6Wdgyg%40mail.gmail.com.

[PhistucK]

The timeline presents the information to which I am referring in a very confusing and inconvenient manner and it is full of irrelevant information when debugging request or loading related stuff that hinders debugging and development. It is good for performance tuning, but less for request or loading related debugging, since you are overloaded with information.

☆PhistucK

To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/CAEX3KhZ%2BRGDj3fJtioP3-ZQddg5arFxO9zGaE6zd-MYAuEGcng%40mail.gmail.com.