Re: [quicwg/base-drafts] DATA frame encoding is inefficient for long dynamically generated bodies (#1885)

[Mike Bishop <[e-mail]>]

Technically, don't you have to declare in your header whether there will be trailers and what they will be?  So that is actually known if you're parsing the HTTP semantic layer.  However, this layer of the mapping doesn't attempt to encode it.

@martinthomson, that's another way to do it, but it makes me very nervous to say that we can't tell the difference between intent and a bug.  Seems like a door to a security risk or at least potential consistency concerns.  Consider a proxy whose back-end connection is interrupted and closes the stream before the entire payload has been transferred -- that error gets propagated and looks like a normal, intended response under those rules.

(Of course, if the proxy wrote a zero length and then had that happen, the same issue would exist.)

-- 
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/1885#issuecomment-431882189