W3C home > Mailing lists > Public > public-webappsec@w3.org > June 2013

Re: CSP: error handling

From: Adam Barth <w3c@adambarth.com>
Date: Tue, 25 Jun 2013 21:22:34 -0700
Message-ID: <CAJE5ia9NxdP0CaxbXeVpZRudPfR7Kzv=MLEjf7Zrh6m-pH1uGQ@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: "Hill, Brad" <bhill@paypal-inc.com>, Mike West <mkwst@google.com>, "dveditz@mozilla.com" <dveditz@mozilla.com>, Ian Melven <imelven@mozilla.com>, WebAppSec WG <public-webappsec@w3.org>
On Tue, Jun 25, 2013 at 3:34 AM, Anne van Kesteren <annevk@annevk.nl> wrote:
> On Tue, Mar 19, 2013 at 12:12 AM, Anne van Kesteren <annevk@annevk.nl> wrote:
>> On Mon, Mar 18, 2013 at 2:42 PM, Hill, Brad <bhill@paypal-inc.com> wrote:
>>> Will this cause retries, even though the intent is not to load the content?
>> For EventSource it would, yes.
>> For XMLHttpRequest though I think I would prefer an error event or
>> NetworkError exception (in case of synchronous) if the request failed
>> because of this rather than load coupled with status 400...
> I never heard back on this. Similar for some other feedback I gave. Is
> there a better way to get the WG to look at feedback?

Perhaps we should use the bug tracker or the issue tracker to ensure
that we address all feedback?  We review the open issues and actions
periodically.  The chairs might have thoughts about how best to manage
this process.

Received on Wednesday, 26 June 2013 04:23:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:54:33 UTC