Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Discovering Maximum Frame Size #28

martinthomson opened this Issue Feb 19, 2013 · 4 comments


None yet
4 participants

martinthomson commented Feb 19, 2013

HTTP/2.0 requires that implementations support a minimum frame size of 8192 bytes. The draft does not specify how an implementation is expected to learn that its peer has limited frame sizes other than by trial and error. Using RST_STREAM causes the error to be discovered after the problem has been encountered.

It's also not possible to use RST_STREAM to reject a too-large frame that is not bound to a specific stream.

This could be indicated in the SETTINGS frame.


mnot commented Feb 27, 2013

Can you bring this up on-list, please?

jpinner commented Feb 28, 2013

Since frame sizes have decreased to 64k maximum down from 16M, is it reasonable to drop this from the spec entirely and require implementations to handle full-sized frames?


grmocg commented Mar 4, 2013

64k is a large amount for an embedded device (but then again it shouldn't be receiving that much data then, probably)?

This was referenced Mar 11, 2013


mnot commented Jun 13, 2013

Discussed at SF Interim; max frame size is fixed.

@mnot mnot closed this Jun 13, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment