Re: [fetch] Provide opt-in for Expect = "100-continue" (#41)

No, it doesn't. 

Expect/Continue is a mechanism for avoiding unnecessary *transfer* of the request body; it won't help you avoid buffering it.

I think what you want to do is assure that developers can use expect/continue. It *might* be useful to have fetch do it natively too, but I think it's a very implementation-specific decision.

Question: How does Fetch handle these sorts of genuinely optional, implementation-specific behaviours? In other places I see hand-waving about "do whatever HTTP stuff you want to do", but here it's pretty intrusive into the request handling model. 

I suppose you might do that by putting a note in to the effect "You can make an implementation choice to support Expect/Continue HERE, but we leave the details as an exercise for the reader."

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/41#issuecomment-155957838