From what I can tell with some Googleing, CORB is very similar to CORS in that it's a server side config issue that can not be fixed on from the client-side. It can be worked around for development purposes, but that is not a fix.
Take a look at this Stackoverflow thread
Thanks John, it used to work till last week, suddenly it started showing CORB warning on the console.
Does it indicate browser security is increased with browser version upgrade
or something changed on API restrictions..?
It looks to me like Browser restrictions as explained in below post . the response of webservice contains X-Content-Type-Options: nosniff -> So browser is blocking XML content
That was my thinking, yes. It looks like Chrome has increased it's default security settings in recent updates. Whenever I start seeing something different these days, and there hasn't been a change in the code, I immediately check to see if the browser auto-updated on me.