Re: [whatwg/fetch] Define behavior in the presence of TLS Early Data (#888)

We always buffer the request body (needed for how we do redirects and potentially also 403), except when the request body is an explicit stream in which case we fail for those cases.

It seems to me that we'd always retry when seeing a 425 based on this, except when there was an explicit request body stream. In that case we'd have to pass it on to the caller? Potentially, we should also avoid making early data requests in this case and making that opt-in.

It's unclear how we should handle erroneous scenarios from the RFC. I guess retry is the way to go, and passing on the 425 when we can't retry due to a request body stream.

-- 
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/888#issuecomment-480217767