Getting CORBs warning on pixel in Web-app (content type different when run directly in Browser and works as designed)?

I'm trying to figure out how to resolve a CORBS warning I'm getting based on Floodlight Marketing Tags. Here is the issue. I have pixel A, which is the initial pixel and it loads In the web app:

Pixel A ==> https://4587700.fls.doubleclick.net/...
Pixel A Content-Type ==> text/html
Pixel A redirects to Pixel B which has the same host and same content type.

Pixel B ==> https://4587700.fls.doubleclick.net/...
Pixel B Content-Type ==> text/html

And Pixel B throws a CORBs warning that Pixel B's response was blocked and Pixel C is not piggy-backed by Pixel B (which it should be).

==============

If I drop Pixel A in the browser address bar, it functions as expected. Directly in the browser:

Pixel A ==> https://4587700.fls.doubleclick.net/...
Pixel A Content-Type ==> text/html
Pixel A redirects to Pixel B which has same host but different content type.

Pixel B ==> https://4587700.fls.doubleclick.net/...
Pixel B Content-Type ==> document
Pixel B loads Pixel C which has facebook hostname but different content type.

Pixel C ==> https://www.facebook.com/...
Pixel C Content-Type ==> gif
==============
Here is the message I get which corresponds to Pixel B:

Cross-Origin Read Blocking (CORB) blocked cross-origin response https://4587700.fls.doubleclick.net/activityi;dc_pre=CM3pmtTmgugCFQ1B4AodPtwDog;src=4587700;type=ccb;cat=ccbartic;u11=https%3A%2F%2Fperspectives.bankofthewest.com%2Finternational-finance%2Fserving-segment-of-one;u12=0;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;npa=;ord=435926103515.3517 with MIME type text/html. See https://www.chromestatus.com/feature/5629709824032768 for more details.

==============

So first of all, why is the content type different for Pixel B when I drop Pixel A directly in the browser compared to pixel A being invoke via the web app?

Can this content-type be the reason I'm getting the CORBS warning and the response of Pixel B being blocked?

Any ideas what can be done to eliminate this CORBs issue in the web app?


Thanks!