W3C home > Mailing lists > Public > public-web-perf@w3.org > June 2014

Re: [Beacon] Off-line behavior, captive portals and error recovery

From: Ilya Grigorik <igrigorik@google.com>
Date: Tue, 3 Jun 2014 11:39:16 -0700
Message-ID: <CADXXVKoQbUqscfzwsyAmDuUwb7ySJv9_x1cvyG+rYJn8KbXg=g@mail.gmail.com>
To: Arvind Jain <arvind@google.com>
Cc: Jonas Sicking <jonas@sicking.cc>, Kornel LesiƄski <kornel@geekhood.net>, public-web-perf <public-web-perf@w3.org>
On Tue, Jun 3, 2014 at 11:05 AM, Arvind Jain <arvind@google.com> wrote:

> 1) Re. 407, what should be the behavior? If the beacon response is a 407,
> should we display an authentication dialog given that the site may have
> gone away? Anne asked whether there should be a flag for it in fetching
> layer. What are we doing today in Mozilla's implementation?


Personally, I think the beacon should fail silently on 407. If we popup an
auth box, the user has zero context where it came from because the beacon
request is invisible to them. In the best case, this is just annoying, in
the worst case, this can mislead the user into giving away credentials
where they shouldn't have (should I type in auth details for current site,
or beacon URL, what is this beacon URL anyway, and what's a beacon? And so
on...).

ig
Received on Tuesday, 3 June 2014 18:40:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:38 UTC