Re: [whatwg/fetch] How should the ReadableStream from response.body work when it's multipart? (#1021)

Hmm, I tried to make a test case but browsers seem to instead get confused.

https://wooded-malleable-mine.glitch.me/ writes out the response body

```
--myboundary
Content-Type: text/plain
Content-Length: 4

aaaa--myboundary
Content-Type: text/plain
Content-Length: 4

bbbb--myboundary
Content-Type: text/plain
Content-Length: 4

cccc--myboundary
Content-Type: text/plain
Content-Length: 4

dddd
```

with header

```
content-type: multipart/x-mixed-replace; boundary=--myboundary
```

But when I head there and put the following in my console

```js
fetch("https://wooded-malleable-mine.glitch.me/").then(r => r.arrayBuffer()).then(console.log)
```

I get a zero-length ArrayBuffer. So either I set up my server wrong (code [here](https://glitch.com/edit/#!/wooded-malleable-mine?path=server.js)) or we have more foundational problems with the Fetch API + multipart/x-mixed-replace.

-- 
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-617405409