UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36
Steps to reproduce the problem:
Test CSP capabilities by trying to set an EventSource to a blocked URL.
What is the expected behavior?
Quietly fail, no thrown error.
What went wrong?
Chrome is throwing an error while Firefox just quietly fails.
Did this work before? N/A
Chrome version: 53.0.2785.116 Channel: canary
OS Version: 10.0
Flash Version: Shockwave Flash 23.0 r0
Refer to https://github.com/w3c/webappsec-csp/issues/120 From mikewest: Indeed. We originally were throwing in XHR, EventSource, etc. @annevk convinced me to change it a million years ago, as it aligns the behavior between redirect blockage and non-redirect blockage, and simplifies the interface to Fetch. I thought we updated Chrome, but it's entirely possible that we didn't.
In other words, this sounds like a Chrome bug and not a spec bug. If you file a bug against Chrome, I'll get it fixed.
Comment 1 by kenrb@chromium.org
, Sep 30 2016Labels: -Type-Bug-Security -Restrict-View-SecurityTeam Type-Bug
Owner: mkwst@chromium.org
Status: Assigned (was: Unconfirmed)