Re: [whatwg/fetch] Define RST_STREAM's error code (#637)

So instead of

> If actualResponse’s status is not 303, request’s body is not null, and the connection uses HTTP/2, then user agents may, and are even encouraged to, transmit an RST_STREAM frame. 

we could maybe have

> If actualResponse’s status is not 303, request’s body is not null, and the connection uses HTTP/2, then user agents may, and are even encouraged to, signal to the server that _response_'s message can be incomplete.

That seems quite awkward to me though.

-- 
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/637#issuecomment-770649387