[whatwg/fetch] processResponseConsumeBody and opaque responses (Issue #1446)

I noticed today that fetching scripts in HTML uses this and while it currently seemingly ignores the second argument that seems like a bug as the body on which it tries to operate will have been consumed.

However, it might be somewhat surprising we end up revealing the full byte sequence of opaque responses to callers without any kind of ceremony.

Not really sure how to address this other than add some "be careful" words around this.

@noamr @domenic thoughts?

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

Message ID: <whatwg/fetch/issues/1446@github.com>