Some requests are returning a CORB error for responses containing text content type

[MSNev]

Need to investigate why the server is returning a CORB error for the response from the sendBeacon code.

[MSNev]

Split this out from the discussion occurring in #1595

[MSNev]

I have found a few related bugs, but have not been able to reproduce with chrome v93.

And in the release notes for v93 I am seeing the following, which seems to suggest that it was a bug in chrome (that is now fixed)

Only apply CORB to no-cors requests (stop applying to CORS requests).

OOR-CORS is now secure against malicious renderers (e.g. the CL
description of https://crrev.com/c/2917236 and
https://crrev.com/c/2925752). This means that CORS doesn't need to
depend on CORB as a defense-in-depth. Because of this, we can restrict
CORB to no-cors requests.

In particular, after this CL:

1. CORB will no longer inspect the Access-Control-Allow-Origin
   response header and will only apply to no-cors requests.

2. CORB will no longer inspect the Cross-Origin-Read-Policy (CORP)
   response header:

   • The CORP-based CORB-opt-in heuristic is no longer needed for CORS
     requests
   • CORP already applies to no-cors requests (independently from
     CORB).

Fixed: 953315
Change-Id: I12c79f9708a67ce341ac1d8366ae4a6c498fc83a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2985760
Auto-Submit: Łukasz Anforowicz lukasza@chromium.org
Reviewed-by: Karan Bhatia karandeepb@chromium.org
Reviewed-by: Charlie Reis creis@chromium.org
Reviewed-by: Matt Menke mmenke@chromium.org
Commit-Queue: Łukasz Anforowicz lukasza@chromium.org
Cr-Commit-Position: refs/heads/master@{#897555}

[MSNev]

Hmm, after manually installing Chrome v92 I can now readily reproduce even when going back to Chrome v93 -- still investigating

[MSNev]

Confirmed: This only occurs for the sendBeacon() commands and it appear to be because the browser doesn't get a the response (so it's empty) and as per the details on the chrome site this warning can be ignored

[MSNev]

v2.7.0 is not fully deployed to NPM and all CDN endpoints

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.