W3C home > Mailing lists > Public > public-webappsec@w3.org > December 2014

Re: [SRI] Towards v1 - do we need error reporting?

From: Brad Hill <hillbrad@gmail.com>
Date: Wed, 10 Dec 2014 20:57:52 +0000
Message-ID: <CAEeYn8hnHjxhDtkgio6q8okunHx1vCB+0sG5or+wbM4fxvpQ5Q@mail.gmail.com>
To: Devdatta Akhawe <dev.akhawe@gmail.com>, Ben Toews <btoews@github.com>
Cc: Frederik Braun <fbraun@mozilla.com>, "public-webappsec@w3.org" <public-webappsec@w3.org>
+1 on error reporting.  Especially as this is an experiment, I think it
will be important to allow individual content providers to gather and
report on their experiences with the spec, not just rely on browser vendor
telemetry.

On Wed Dec 10 2014 at 11:09:04 AM Devdatta Akhawe <dev.akhawe@gmail.com>
wrote:

> +1 on error reporting.
>
> On 10 December 2014 at 10:38, Ben Toews <btoews@github.com> wrote:
> > I think error reporting would be nice. Otherwise it would be hard to
> detect
> > if the resource host decided to return difference content based on
> > user-agent or something weird like that.
> >
> > On Wed, Dec 10, 2014 at 10:41 AM, Frederik Braun <fbraun@mozilla.com>
> wrote:
> >>
> >> I am leaning towards taking the current state and calling it a v1 around
> >> January (see other email: I have started another thread about
> >> noncanonical-src and fallbacks just before this one)
> >>
> >> But we are not sure whether that should include error reporting (in a
> >> similar way that CSP does it).
> >>
> >> So, the question is: What do web developers want?
> >>
> >>
> >>
> >>
> >>
> >
>
>
Received on Wednesday, 10 December 2014 20:58:19 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:08 UTC