Re: Intent to implement: report-to header as part of Reporting API

2019-01-13 Thread Andrea Marchesini
> > > Sorry for my laziness not having scanned through the links below to find > the answer to this question, but how does this interact with the > same-origin policy, if at all? And if it does, is enabling it in sandbox > iframes without the allow-same-origin token the right thing to do? > It's

Re: Intent to implement: report-to header as part of Reporting API

2019-01-10 Thread Ehsan Akhgari
On Thu, Jan 10, 2019 at 7:27 AM Andrea Marchesini wrote: > Summary: Reporting API offers 2 ways to obtain reports: ReportingObserver > and Report-to Header. I implemented ReportingObserver months ago and I sent > a separate intent-to-implement email about it. This email is about > "report-to"

Re: Intent to implement: report-to header as part of Reporting API

2019-01-10 Thread Andrea Marchesini
We have some WPTs here: https://searchfox.org/mozilla-central/source/testing/web-platform/tests/content-security-policy/reporting-api/ My tests are here: - gtests: https://searchfox.org/mozilla-central/source/dom/reporting/tests/gtest - mochitests:

Re: Intent to implement: report-to header as part of Reporting API

2019-01-10 Thread David Burns
On Thu, 10 Jan 2019 at 12:27, Andrea Marchesini wrote: > web-platform-tests: just a little support. I wrote several mochitests which > can be converted to WPTs with a bit of effort. > There don't appear to be any WPT if I am looking in the right place[1]. Since Google are experimenting it feels

Intent to implement: report-to header as part of Reporting API

2019-01-10 Thread Andrea Marchesini
Summary: Reporting API offers 2 ways to obtain reports: ReportingObserver and Report-to Header. I implemented ReportingObserver months ago and I sent a separate intent-to-implement email about it. This email is about "report-to" header, which allows a server to specify a set of endpoints to