[quicwg/base-drafts] Truncated http stream error handling is aggressive (#2718)

[MikkelFJ <[e-mail]>]

HTTP draft sect. 6.1

> These streams carry frames related to the request/response (see Section 4.1). When a stream terminates cleanly, if the last frame on the stream was truncated, this MUST be treated as a connection error (see HTTP_MALFORMED_FRAME in Section 8.1). 

I can see the point of always sending the header fields of a frame, but if a data frame is required to be sent in full or have the connection closed, it is hard for a server to stop a cancelled request without having the connection closed when it sends an entire file in a single data frame.

Splitting up files into multiple frames ought to be done because the length is not known in advance, not to avoid connection close.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/2718