Re: [whatwg/fetch] Clarify the way CORB should be applied to beacons (#882) from Mike Sidorov on 2019-03-19 (public-webapps-github@w3.org from March 2019)

From: Mike Sidorov <notifications@github.com>
Date: Tue, 19 Mar 2019 15:58:34 +0000 (UTC)
To: whatwg/fetch <fetch@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/fetch/issues/882/474441525@github.com>

We have 2 domains - `site.xyz` sending tracking data to `cool-analytics.xyz` with beacon requests. We also send debug data in response, simple JSON object like `{"id": 123}`. Now this becomes unreadable in latest Chrome because
- we cannot send `application/json` or any other non-CORS-safelisted mimetype since Chrome doesn't support that (and that's a [known bug](https://bugs.chromium.org/p/chromium/issues/detail?id=490015))
- since we're using "default" mimetype CORB blocks the response data.

Sure thing it needs fixing in Chrome/Chromium but at least CORB part is done by spec.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/882#issuecomment-474441525

Received on Tuesday, 19 March 2019 15:59:00 UTC