Re: [quicwg/base-drafts] Replace HTTP_MALFORMED_FRAME error code (#2662)

[Lucas Pardue <[e-mail]>]

> I think my preference goes to merging INVALID_PRIORITY with FRAME_ERROR. 
Thanks for the feedback. It's an easy change to make. I'll wait for some supporting or dissenting voices but otherwise will do this.

> Regarding rearranging the numbers, I wonder if it would be possible to split the error codes into two groups: connection-level error codes and stream-level ones. In contrary to HTTP/2, most of the HTTP/3 error code are either a connection-level error code or a stream-level error code, not both.

This resonates with my earlier analysis. Some of this was captured in https://github.com/quicwg/base-drafts/issues/2816. But I think what you are suggesting is a slightly different thing. Can you explain what splitting might look like and how it would help? I think it gets complicated because 1) we may have a proxy that is trying to translate errors between H2 and H3. 2) stream errors can be upgraded 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/pull/2662#issuecomment-507282456