Reuest.body value after passed to another Request

[yutakahirano]

req2 = new Request(req);

At whatwg/fetch#61, we agreed that

• req.bodyUsed should be false if req had null body, and
• req.bodyUsed should be true if req had a non-null body.

Anne proposed to introduce obsolete flag in order to make req.body null and req.bodyUsed true after passing the body, but it looks like another passed flag we replaced with ReadableStream.IsDisturbed. @jakearchibald's piping idea sounds cleaner to me and ideally it should work, but I'm not sure about its performance.

Thoughts?

cc: @domenic @wanderview @tyoshino

[yutakahirano]

cc: @annevk

[annevk]

I'm okay either way. I guess someone should measure the performance of doing piping if we are fine gating on that?

[domenic]

Is this solved currently? I lost track. If it is not, it probably can be solved similarly to w3c/ServiceWorker#934 ?

[yutakahirano]

It's not yet solved, and it should be solved as same as w3c/ServiceWorker#934.

[annevk]

What is the status of this issue? I missed it while merging in stream-based requests.