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.

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

Which HTTP/2 settings must be rejected? #4811

Merged
merged 1 commit into from
Jan 25, 2021
Merged

Which HTTP/2 settings must be rejected? #4811

merged 1 commit into from
Jan 25, 2021

Conversation

MikeBishop
Copy link
Contributor

Specifically those defined in RFC 7540.

@MikeBishop MikeBishop added editorial An issue that does not affect the design of the protocol; does not require consensus. -http labels Jan 22, 2021
@MikeBishop MikeBishop linked an issue Jan 22, 2021 that may be closed by this pull request
Possible ambiguity for Handling Reserved HTTP/2 Settings parameters type values #4809
Closed
@MikeBishop MikeBishop merged commit f0423a4 into master Jan 25, 2021
@MikeBishop MikeBishop deleted the http/reservation_precision branch January 25, 2021 20:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@martinthomson martinthomson martinthomson approved these changes

Assignees
No one assigned
Labels
-http editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Possible ambiguity for Handling Reserved HTTP/2 Settings parameters type values
2 participants
@MikeBishop @martinthomson