Re: [quicwg/base-drafts] Some correctness issues in the HTTP/3 drafts are stream errors, not connection errors (#2511)

[ianswett <[e-mail]>]

The current text is:
"encountering a larger message header SHOULD be treated as a stream error of type "HTTP_EXCESSIVE_LOAD".  If an implementation wishes to advise its peer of this limit, it can be conveyed as a number of bytes in the "SETTINGS_MAX_HEADER_LIST_SIZE" parameter."

To me, the issue here is that a peer can have a limit, but is not required to advertise that limit.  If we required that if a peer has a limit, it must advertise it and enforce it, then closing the connection makes sense to me.

Given it's really easy to advertise it and it's within encryption, I don't see any reason not to make that change, but it's a slightly larger change than the other cases, where we're changing obviously avoidable errors to connection errors.

-- 
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/2511#issuecomment-471181593