W3C home > Mailing lists > Public > public-webappsec@w3.org > October 2012

Re: Trigger a DOM event/error when a CSP violation happens.

From: Eduardo' Vela <evn@google.com>
Date: Thu, 25 Oct 2012 08:09:23 -0700
Message-ID: <CAFswPa8GwWaQRNN3WHNr2efDJ3CgB636Y-6XV=ypXSeFfv6USg@mail.gmail.com>
To: Mike West <mkwst@google.com>
Cc: public-webappsec@w3.org, Adam Barth <w3c@adambarth.com>
With DOM events we can track which element with which value triggered the
report.
On Oct 25, 2012 7:54 AM, "Mike West" <mkwst@google.com> wrote:

> On Thu, Oct 25, 2012 at 4:49 PM, Eduardo' Vela <evn@google.com> wrote:
>
>> The console warnings are nice, but when we receive tens of millions of
>> reports, its hard to find duplicates and its hard to reproduce.
>>
> If the issue is a flood of violation reports, I don't understand how
> client-side DOM events would help you.
>
> Can you give a more detailed description of the problem and how DOM events
> fit into a solution?
>
> --
> Mike West <mkwst@google.com>, Developer Advocate
> Google Germany GmbH, Dienerstrasse 12, 80331 München, Germany
> Google+: https://mkw.st/+, Twitter: @mikewest, Cell: +49 162 10 255 91
>
>
Received on Thursday, 25 October 2012 15:09:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 25 October 2012 15:09:51 GMT