Re: [whatwg/fetch] CORB blocking JSON response after redirect (#854)

*Sigh*

Turns out it was indeed a CORS issue.  Apparently setting the fetch request to `no-cors` emits an `opaque` response which, according to [your docs](https://fetch.spec.whatwg.org/#concept-filtered-response-opaque), disallows you from receiving basically any data.  I'm guessing this is where the CORB intervened, as it most likely saw the response was supposed to be opaque, and when it wasn't, threw out an alarm.  Wish I saw that sooner.

I've got CORS configured properly on my server and all is well now.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/854#issuecomment-450512225