cy.intercept doesn't handle binary data correctly

[simfeld]

Current behavior

1. When intercepting a request that returns binary data (for example application/octet-stream) the response is corrupted by cy.intercept.
2. When trying to stub a request with an ArrayBuffer it is interpreted as JSON.

Desired behavior

1. Intercepting a request does not alter the response if it is not stubbed.
2. It is possible to supply an ArrayBuffer to an intercept stub.

Test code to reproduce

Reproduction code is here: https://github.com/simfeld/cypress-intercept-binary. There are three tests:

1. no intercept: This test succeeds, the response is loaded correctly from the server.
2. intercept without stub: This test fails. The request is intercepted but not stubbed. The response that arrives in the browser is {} or [123, 125] when interpreted as ArrayBuffer, instead of the response that the server delivers.
3. intercept with stub: This test fails. The request is intercepted and a stub is returned. The response that arrives in the browser is {} or [123, 125] when interpreted as ArrayBuffer, instead of the stub supplied to the intercept.

Versions

Latest version as of filing this issue (7.4.0)

Related issues

This issue is possibly related: #15038

[simfeld]

Did some digging and found the issue causing intercept to corrupt the response. See draft #16755. With this change the second test "intercept without stub" in the reproduction project passes (while the third one still fails).

[cypress-bot]

The code for this is done in cypress-io/cypress#16755, but has yet to be released.
We'll update this issue and reference the changelog when it's released.

[cypress-bot]

Released in 7.6.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v7.6.0, please open a new issue.