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

Re: Correct Server-Timing headers

From: Anton Nemtsev <newsilentimp@gmail.com>
Date: Tue, 13 Feb 2018 13:00:22 +0200
Message-ID: <CA+JO0fL-+uWa2Mv9MnWQ1-jaPR00dEdFOc+2Dm69kH2gMF2VLA@mail.gmail.com>
To: Charles Vazac <cvazac@gmail.com>, public-web-perf <public-web-perf@w3.org>
> Devtools aligns to the spec changes starting in version 65. I suspect you
are on an earlier version.

Yes, it was the case. I test it in chrome 64.
In the canary headers work as prescribed.


On Mon, Feb 12, 2018 at 10:59 PM, Charles Vazac <cvazac@gmail.com> wrote:

> Devtools aligns to the spec changes starting in version 65. I suspect you
> are on an earlier version.
>
> On Mon, Feb 12, 2018 at 9:50 AM, Ilya Grigorik <igrigorik@google.com>
> wrote:
>
>> 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.
>>
>> ig
>>
>> On Sun, Feb 11, 2018 at 4:52 AM, Anton Nemtsev <newsilentimp@gmail.com>
>> wrote:
>>
>>> 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 Tuesday, 13 February 2018 12:59:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 February 2018 12:59:13 UTC