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.

Sign up for GitHub

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

Jump to bottom

Strictify implementation WRT to the RFC #9

Open

lucasdicioccio opened this issue Aug 13, 2017 · 0 comments

Labels

enhancement question

Member

lucasdicioccio commented Aug 13, 2017

We should make the http2-client library adhere more strictly to the RFC when the server sends bogus frames.

This is a meta bug and we should consider whether it's fine to be strict, loose, or let users pick whether to error on things like:

unwanted frames on idle/closed streams
increasing IDs only
invalid settings
invalid window in flow-control
invalid frame sizes
data-consumed out of flow-control limits
authority of push promise https://tools.ietf.org/html/draft-ietf-httpbis-http2-17#section-10.1
...

We should consider the performance/code readability trade-offs thoroughly on a case-by-case basis.

The text was updated successfully, but these errors were encountered:

lucasdicioccio added enhancement question labels

lucasdicioccio mentioned this issue

How would I trust the correctness of this library without any testing? #16

Closed

lucasdicioccio mentioned this issue

Dispatch more #44

Merged

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