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

Allow maxStreamID to be used in GOAWAY by either peer. #102

Merged
merged 1 commit into from
Apr 16, 2019

Conversation

Lukasa
Copy link
Contributor

@Lukasa Lukasa commented Apr 16, 2019

Motivation:

We would previously error if clients emitted a GOAWAY frame that had
a last stream ID set to the max value. This is a bit unnecessary, not
least given that we emitted those frames ourselves! In fact, this error
would mask real server protocol errors if we hit them.

Modifications:

  • Allowed max stream ID as the last stream ID.
  • Wrote a test to verify this.

Result:

Fewer unnecessary protocol errors.
Resolves #101.

Motivation:

We would previously error if clients emitted a GOAWAY frame that had
a last stream ID set to the max value. This is a bit unnecessary, not
least given that we emitted those frames ourselves! In fact, this error
would mask real server protocol errors if we hit them.

Modifications:

- Allowed max stream ID as the last stream ID.
- Wrote a test to verify this.

Result:

Fewer unnecessary protocol errors.
@Lukasa Lukasa added the semver/patch No public API change. label Apr 16, 2019
@Lukasa Lukasa added this to the 1.2.0 milestone Apr 16, 2019
@Lukasa Lukasa requested a review from weissi April 16, 2019 16:44
Copy link
Member

@weissi weissi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice one

@weissi weissi merged commit 4298626 into apple:master Apr 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
semver/patch No public API change.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Hitting an inbound connection error can lead to InvalidStreamIDForPeer errors when acting as a client.
2 participants