"Failed to load resource" - more information wanted

[helm...@gmail.com]

Hi Group!

Whenever I get a 404, the console reports "Failed to load resource: the

server responded with a status of 404 (Not Found) [url]" which is ..

lacking information.

I want to know what requested the resource (image/script/..) so I know

where to look: through the HTML or js, or perhaps some auto-generated

.sass-files? Would that be feasible to implement?

The current implementation is useless for me since the network tab already

marks the faulty request red.

Cheers,

Carl

[Vsevolod Vlasov]

A typical not found message looks like this:

GET http://localhost/html/resources/not_found.html 404 (Not Found) /var/www/html/test/xhr-html.js:60

A last link here should show you a script that triggered this request (e.g. XMLHttpRequest.send() method call).

The first link here should show you this request on the network panel where initiator panel will (sometimes) show you where this request was initiated.

It does not support all possible initiator types, but it usually works for resources loaded while parsing HTML document ("Parser" type).

It works for scripts as 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.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Benjamin Smith]

When the message looks like that it is obviously trivial to solve the OPs problem. When the message looks like this:

Failed to load resource: the server responded with a status of 404 (Not Found) http://domain.com/faultyurl.jpg

There is no clear direction to where to look for the problematic reference to the missing resource. What part of the code is calling this resource with a faulty URL? Where do I look to find the problematic code? In other words, why is this 404 different (and less helpful) from the one you're referring to? And can that be changed (or worked around)?

--Ben

[PhistucK]

Without the Developer Tools feature open, you only see the URL that responded with an Error 404 instead of the calling code. I guess this is because no one is instrumenting the errors if you are not debugging, probably in order to prevent the performance overhead that it entails.

If you open the Developer Tools and refresh (assuming that reproduces your Error 404), you should see the calling code.

☆PhistucK

--
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/d8e0f79f-03d1-4047-b514-5fe62686b0ad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.