- From: Domenic Denicola <notifications@github.com>
- Date: Tue, 21 Apr 2020 15:44:38 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 21 April 2020 22:44:50 UTC
After tweaking the demo a bit I'm getting a forever-pending `arrayBuffer()` promise. That's more like what I would expect. I guess then multipart is only observable through the `.body` property. And indeed, at least in Firefox and Chrome, that displays raw chunks. (Although I'm seeing skipped chunks... probably a bug in my server code or the CDN/proxy in front of Glitch.) OK. So we can come back to the OP's question as to whether we want to expose any built-in helpers in fetch (e.g. a transform stream) that lets people parse `multipart/x-mixed-replace` responses... -- 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/1021#issuecomment-617451072
Received on Tuesday, 21 April 2020 22:44:50 UTC