[Bug][skywalking-client-js]broke when I request a cross domain request （arraybuffer）

[Mikey-Lucky]

Search before asking

• I had searched in the issues and found no similar issues.

Apache SkyWalking Component

NodeJS Client Side Agent (apache/skywalking-client-js)

What happened

When I request a cross domain request,the console display that "Uncaught InvalidStateError: Failed to read the 'responseText' property from 'XMLHttpRequest': The value is only accessible if the object's 'responseType' is '' or 'text' (was 'arraybuffer')".The stack display the error is generated by ”Ajax Error Collection“.

What you expected to happen

index.js:1 Uncaught InvalidStateError: Failed to read the 'responseText' property from 'XMLHttpRequest': The value is only accessible if the object's 'responseType' is '' or 'text' (was 'arraybuffer').
at eval (index.js:1:6619)
at XMLHttpRequest.f (index.js:1:22756)
at XMLHttpRequest.eval (index.js:1:20573)

How to reproduce

let xhr= new XMLHttpRequest();
xhr.open('GET','...',true);// blocked by CORS
xhr.responseType = 'arraybuffer';
xhr.send();

Anything else

No response

Are you willing to submit a pull request to fix on your own?

• Yes I am willing to submit a pull request on my own!

Code of Conduct

• I agree to follow this project's Code of Conduct

[wu-sheng]

Why a cross domain is reported to us?

[Mikey-Lucky]

The requested address comes from the server, and sometimes cross domain situations may occur in the testing environment. Actually, we don't know if one day it will appear in the production environment due to some mistakes.

[wu-sheng]

// Report collected data to `http:// + window.location.host + /browser/perfData` in default
ClientMonitor.register({
  # Use core/default/restPort in the OAP server.
  # If External Communication Channels are activated, `receiver-sharing-server/default/restPort`,
  # ref to https://skywalking.apache.org/docs/main/latest/en/setup/backend/backend-expose/
  collector: 'http://127.0.0.1:12800', 
  service: 'test-ui',
  pagePath: '/current/page/name',
  serviceVersion: 'v1.0.0',
});

This is the address the client agent is going to access. That is all we do. And you are the one adding this to suitable pages of your web app.

[Mikey-Lucky]

I'm very sorry, but I think you misunderstood. I did it this way, cross domain requests are not for collection purposes, but for our normal business requests. When our normal business requests cross domains and are 'arraybuffer', it will cause the collection requests to not work properly.

[Mikey-Lucky]

[Mikey-Lucky]

The screenshot I took is just one of the situations, in fact, knowing that problems will occur across domains will lead to them

[wu-sheng]

We will handle this. but I don't think this exception should cause an error when collecting through Skywalking, right?

I don't know that part.

[Mikey-Lucky]

The second mistake comes from Skywalking

[wu-sheng]

I saw that, but can't tell why is that.

[Mikey-Lucky]

I understand, thank you for your answer