Server-Timing data incorrectly rendered in Devtools timing panel
Reported by
andrew.b...@gmail.com,
Jul 19 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 Steps to reproduce the problem: 1. Navigate to the following URL with devtools open: https://httpbin.org/response-headers?server-timing=source;foo,%20edgeID;cache-lcy9384-LCY,%20edgeDatacenter;LCY,%20edgeIP;10.101.1.209,%20edgeCacheState;HIT-CLUSTER,%20edgeStaleInfo;(null),%20edgeObjectDigestRatio;0.137,%20edgeVCLVer;39Mzqa4U.60_88-3a2974b9c9d1c7,%20edgeElapsedTimeMS=3,%20edgeObjCacheHitCount;1,%20edgeObjTTL;31536000.000,%20edgeObjSWR;60.000,%20edgeObjSIE;86400.000,%20edgeObjAge;3844,%20edgeObjDateCreated;1500303811,%20edgeObjRemainingTTL;,%20edgeObjRemainingSWR;,%20edgeObjRemainingSIE;,%20clientIP;10.1.132.132,%20clientLat;91.515,%20clientLng;-4.083,%20clientCity;london,%20clientBrowserName;Chrome,%20clientBrowserVer;,%20clientIsMobile;0,%20backendID;cluster_london_city_uk,%20backendHealthy;1,%20backendIP;10.1.135.126,%20backendName;39MzaFBISKerFJYsF&server-timing=backendExecTimeMS=23 Alternatively, if the httpbin.org service is no longer available, create a URL whose HTTP response includes two `Server-Timing` headers, as follows: Server-Timing:backendExecTimeMS=23 Server-Timing:source;foo, edgeID;cache-lcy9384-LCY, edgeDatacenter;LCY, edgeIP;10.101.1.209, edgeCacheState;HIT-CLUSTER, edgeStaleInfo;(null), edgeObjectDigestRatio;0.137, edgeVCLVer;39Mzqa4U.60_88-3a2974b9c9d1c7, edgeElapsedTimeMS=3, edgeObjCacheHitCount;1, edgeObjTTL;31536000.000, edgeObjSWR;60.000, edgeObjSIE;86400.000, edgeObjAge;3844, edgeObjDateCreated;1500303811, edgeObjRemainingTTL;, edgeObjRemainingSWR;, edgeObjRemainingSIE;, clientIP;10.1.132.132, clientLat;91.515, clientLng;-4.083, clientCity;london, clientBrowserName;Chrome, clientBrowserVer;, clientIsMobile;0, backendID;cluster_london_city_uk, backendHealthy;1, backendIP;10.1.135.126, backendName;39MzaFBISKerFJYsF 2. Switch to the Timing panel in devtools What is the expected behavior? Both keys and values should be displayed for non-timing metrics. What went wrong? For non-timing metrics, only the values are displayed, and some metrics are not visible at all. Did this work before? N/A Chrome version: 59.0.3071.115 Channel: stable OS Version: OS X 10.12.5 Flash Version:
,
Jul 19 2017
Thanks for reporting this, it does look like an implementation gap on our end. On that note, there is an outstanding discussion on whether we should change the format of the header: https://github.com/w3c/server-timing/issues/12#issuecomment-309138002 -- would appreciate any thoughts or comments.
,
Jul 19 2017
,
Jul 19 2017
I thought this was fixed already?
,
Dec 14 2017
,
Sep 18
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by andrew.b...@gmail.com
, Jul 19 2017