Re: [Beacon] Required Beacon-Age: handling. from David Benjamin on 2014-08-18 (public-web-perf@w3.org from August 2014)

From: David Benjamin <davidben@chromium.org>
Date: Mon, 18 Aug 2014 13:59:38 -0400
To: Ilya Grigorik <igrigorik@google.com>
Cc: Adam Barth <abarth@chromium.org>, Sigbjorn Finne <sof@opera.com>, Arvind Jain <arvind@google.com>, public-web-perf <public-web-perf@w3.org>
Message-ID: <CAF8qwaAXApMCtNH6MNB0zC1+z+KeAUb=y-PtYgH3m+1Y6tTt7Q@mail.gmail.com>

On Mon, Aug 18, 2014 at 1:51 PM, Ilya Grigorik <igrigorik@google.com> wrote:

> Yes, until there is a bug and some UA omits it by accident (or
> intentionally), at which point I'm back to UA detection: if X UA then no
> delay, if Y UA then I don't trust the timestamp... at which point, I guess
> I would need to move that detection into JS-land and pick the method that I
> trust.
>

Firefox appears to already ship sendBeacon without the Beacon-Age header
anyway. (I imagine their implementation predates the header.)

Received on Tuesday, 19 August 2014 08:31:29 UTC