Server-Timing header interpreted with wrong units
Reported by
dvpdin...@gmail.com,
Mar 22 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3047.0 Safari/537.36 Steps to reproduce the problem: A Server-Timing header of `view=230.5, db=32.9` should be interpreted in milliseconds What is the expected behavior? The DevTools should report 32.9ms in db and 230.5ms in view. What went wrong? The DevTools incorrectly interprets the values as seconds, leading to a result of 32.9s in db and 3.8min in view. Did this work before? No Chrome version: 59.0.3047.0 Channel: dev OS Version: OS X 10.12.3 Flash Version: See https://github.com/WICG/server-timing/issues/11
,
Mar 28 2017
dvpdiner2@ could you please provide a sample test file to triage the issue from TE end. Thanks..
,
Mar 29 2017
This is a simple NodeJS server that can run without dependencies and serves a single text page with a Server-Timing header. It looks like this is working correctly in the current dev channel (59) but it is showing the wrong values in Chrome 56 and 57. Looks like this might have been fixed in the last commit of 594800. I'll try to check Chrome 58 to figure out where I need to return seconds and where I need to return milliseconds.
,
Mar 29 2017
Thank you for providing more feedback. Adding requester "sureshkumari@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 30 2017
,
Apr 6 2017
Hi dvpdiner2, This should have been fixed here: https://codereview.chromium.org/2689833002/ It appears this bug was reported against Chrome 59, which is strange because it should have been fixed in this version. Can you try again and make sure it is still broken?
,
Apr 6 2017
It looks to be working as intended in Chrome 59. Thanks.
,
Apr 6 2017
Thanks! |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ranjitkan@chromium.org
, Mar 27 2017