Resource Timing information is unavailable for 4xx and 5xx resources
Reported by
karthik3...@gmail.com,
Nov 21 2017
|
|||||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36
Steps to reproduce the problem:
1. Run the nodejs server that serves an index.html with two resources both of which should return with a 404.
2. In the devtools network panel, ensure that the resources show up as 404 (and that you can see the network timings)
3. In the Javascript console, fetch the resource timing as: `window.performance.getEntriesByType('resource')`
What is the expected behavior?
The resource timing should include the two resources in the test case (frame1.html and image1.png).
What went wrong?
In Chrome, the resource timing doesn't include resources with 4xx (and possibly 5xx) errors whereas other browsers includes them.
This information is useful for web developers to know not just the fact that their resources failed but also the timings in the case of failed resources. See the attached image for the behavior on Firefox and IE10 (I don't have an Edge browser to confirm).
Did this work before? No
Does this work in other browsers? Yes
Chrome version: 62.0.3202.94 Channel: stable
OS Version: OS X 10.12.6
Flash Version:
,
Nov 21 2017
,
Nov 22 2017
I know this is probably too soon to ask, but I am curious on when we can expect a fix for this issue. Any updates on this is highly appreciated. We are a performance monitoring company and we rely on this heavily for our RUM offering.
,
Nov 22 2017
Able to reproduce this issue on Mac 10.12.6, Win-10 and Ubuntu 14.04 using chrome reported version #62.0.3202.94 and latest canary #64.0.3275.0. This is a non-regression issue as it is observed from M50 old builds. Hence, marking it as untriaged to get more inputs from dev team. Thanks...!!
,
Nov 22 2017
Assigning to tyoshino@ for triage.
,
Nov 27 2017
Marking WontFix as per https://bugs.chromium.org/p/chromium/issues/detail?id=460879#c19, for now. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by tdres...@chromium.org
, Nov 21 2017