CORB: How does a web dev allow cross-origin JSON reads from a trusted source?

[Noel Burgess]

[Disclaimer - I'm way out of my depth when it comes to the more esoteric bits of Internet security and I don't pretend to know what I'm talking about ;)]

Dev, currently 79.0.294.1

At answers.microsoft.com, I see 8-15 calls to web.vortex.data.microsoft.com blocked by CORB on every page load. Each call (many of them concurrent) takes 0.5-5.0s only to end with no response, so I won't believe that this isn't affecting site performance. And presumably the lack of response means that whatever the calls' purpose, they are not providing the data the site wants. I have pointed this out to the site engineers, whose reaction was to point me to old articles about CORS blocking in IE.

There must be a way for them to specify that these calls can be trusted. Is there anything I can do in the browser, or anything I might suggest to the web devs?

Illustration:

[#2]

Vortex is one of our telemetry collection servers.  It may be that your ad blocking tracker blocking may be preventing these from completing.  We use Vortex on the Insider pages to track things like which highlights are most popular, and I am guessing that the Answers site is doing something similar.  Thanks - Elliot

[#3]

@Elliot Kirk  I have seen this also on my RDLC reports. Which causes them to render very slow(2+ minutes). How can I disable that on my RDLC reports, so that they render fast??

I wrote stackoverflow question and explanation on my issue here:

https://stackoverflow.com/questions/70213538/why-my-rdlc-reports-take-a-very-long-time-to-render-eve...

Check the image below and notice the "vortex.data.microsoft.com" requests.

Please help.