W3C home > Mailing lists > Public > public-web-perf@w3.org > February 2018

Re: Correct Server-Timing headers

From: Ilya Grigorik <igrigorik@google.com>
Date: Mon, 12 Feb 2018 07:50:48 -0800
Message-ID: <CADXXVKpsNc8YE1zdPFzGijELDQyPeavCrp_Skvx9wKM5NudjnQ@mail.gmail.com>
To: Anton Nemtsev <newsilentimp@gmail.com>
Cc: public-web-perf <public-web-perf@w3.org>, Charles Vazac <cvazac@gmail.com>
Hi Anton.

This sounds like a Chrome implementation question, can you please
reroute/publish this as a crbug.com? Charles (cc'ed) is the right person to
triage this one on that side.


On Sun, Feb 11, 2018 at 4:52 AM, Anton Nemtsev <newsilentimp@gmail.com>

> Hi
> I am confused a little, from spec I see that header should look like:
> Server-Timing: cache;desc="Cache Read";dur=23.2
> Server-Timing: ssr;desc="Server Side Rendering";dur=60
> But in fact this headers will not show time in a Chrome, only two lines
> 'desc'.
> If I will use header this way:
> Server-Timing: DO_NOT_MATTER=60; desc="SSR";
> I will get `SSR: 60ms` in the Chrome Developer Tools. But why
> DO_NOT_MATTER do not matter?
> And it's kinda differ from spec.
> May you please clarify how I should use this header.
> With all Best Regards.
Received on Monday, 12 February 2018 15:51:51 UTC

This archive was generated by hypermail 2.3.1 : Monday, 12 February 2018 15:51:52 UTC