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

Discuss different paths to closure in HTTP #1599

Closed
MikeBishop opened this issue Jul 24, 2018 · 0 comments
Closed

Discuss different paths to closure in HTTP #1599

MikeBishop opened this issue Jul 24, 2018 · 0 comments
Labels
-http editorial An issue that does not affect the design of the protocol; does not require consensus.

Comments

@MikeBishop
Copy link
Contributor

This is probably an expansion/relocation of the GOAWAY text; offline editorial feedback indicated that it was unclear from the HTTP document when to use GOAWAY vs. APPLICATION_CLOSE vs. CONNECTION_CLOSE, and readers shouldn't need to read the transport doc to figure it out.
@MikeBishop MikeBishop added editorial An issue that does not affect the design of the protocol; does not require consensus. -http labels Jul 24, 2018
@MikeBishop MikeBishop mentioned this issue Aug 28, 2018
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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

No branches or pull requests
1 participant
@MikeBishop