- From: Alex Russell <notifications@github.com>
- Date: Tue, 12 Jun 2018 12:08:16 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 12 June 2018 19:08:40 UTC
Ok, so we spent a bit more time in today's meeting reading the [SH spec](https://tools.ietf.org/html/draft-ietf-httpbis-header-structure-06) and note that it doesn't support any sort of nesting in it's data-structures. Nearly every example in the [Reporting API Explainer](https://github.com/WICG/reporting/blob/master/EXPLAINER.md) involves nesting, and the JS API specifically returns a list of report. It seems that it would be possible to flatten some of these report types to confirm to SH restrictions. The `Report-To` header looks particularly ripe for this. As for report bodies, that's less clear. @mnot: are your concerns with JSON limited to `Report-To`? If bodies are sent in JSON, does that still work for you? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/195#issuecomment-396700380
Received on Tuesday, 12 June 2018 19:08:40 UTC