Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CONTINUATION Frame Size #229

Closed
jasnell opened this issue Aug 12, 2013 · 2 comments
Closed

CONTINUATION Frame Size #229

jasnell opened this issue Aug 12, 2013 · 2 comments

Comments

@jasnell
Copy link
Contributor

jasnell commented Aug 12, 2013

Because sequences of header continuations are required to be contiguous without any interleaving or multiplexing or whatnot... it really does not make sense to limit CONTINUATION frames carrying HTTP headers to 16383 octets, as that needlessly just increases the encoding overhead for continuations. If the END_HEADERS flag is not set, we ought to allow frame sizes up to the maximum allowed (65,535) to eliminate this additional overhead.

@molnarg
Copy link
Contributor

molnarg commented Oct 10, 2013

In this case, you still have to write the code that deals with fragmented HEADERS frames. So I don't think this makes things simpler...

@martinthomson
Copy link
Collaborator

We concluded in Seattle that we didn't want to go with half-measures like this. All frames will be required to be less than 2^14 in size, regardless of the upper layer protocol or frame type.

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

No branches or pull requests

3 participants