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

Resolve off-by-one errors in settings bounds. #97

Merged
merged 1 commit into from
Apr 15, 2019

Conversation

Lukasa
Copy link
Contributor

@Lukasa Lukasa commented Apr 15, 2019

Motivation:

When we're validating that settings are in their bounds, we should probably endeavour to
express those bounds correctly.

Modifications:

  • Fixed the bounds checks on SETTINGS_INITIAL_WINDOW_SIZE and SETTINGS_MAX_FRAME_SIZE.
  • Added regression tests.

Result:

Better correctness.
Resolves #96

Motivation:

When we're validating that settings are in their bounds, we should probably endeavour to
express those bounds correctly.

Modifications:

- Fixed the bounds checks on SETTINGS_INITIAL_WINDOW_SIZE and SETTINGS_MAX_FRAME_SIZE.
- Added regression tests.

Result:

Better correctness.
@Lukasa Lukasa added the 🔨 semver/patch No public API change. label Apr 15, 2019
@Lukasa Lukasa added this to the 1.1.1 milestone Apr 15, 2019
@Lukasa Lukasa requested a review from weissi April 15, 2019 08:39
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.

very nice! thanks

@weissi weissi merged commit 08db9d8 into apple:master Apr 15, 2019
@Lukasa Lukasa modified the milestones: 1.1.1, 1.2.0 Apr 15, 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.

Max frame size can be (1<<24)-1
2 participants