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
Editorial nits for HTTP #3942
Editorial nits for HTTP #3942
Conversation
@@ -2406,7 +2416,7 @@ INADEQUATE_SECURITY (0xc): | |||
: Not applicable, since QUIC is assumed to provide sufficient security on all | |||
connections. | |||
|
|||
H3_1_1_REQUIRED (0xd): | |||
HTTP_1_1_REQUIRED (0xd): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
😁
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
HTTP 3.1.1 for Workgroups, perhaps?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
whoops
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice. A few suggestions, but these are mostly easy or obvious fixes. Feel free to use follow-up issues for the trickier comments.
@@ -2406,7 +2416,7 @@ INADEQUATE_SECURITY (0xc): | |||
: Not applicable, since QUIC is assumed to provide sufficient security on all | |||
connections. | |||
|
|||
H3_1_1_REQUIRED (0xd): | |||
HTTP_1_1_REQUIRED (0xd): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
HTTP 3.1.1 for Workgroups, perhaps?
Co-authored-by: Martin Thomson <mt@lowentropy.net>
draft-ietf-quic-http.md
Outdated
@@ -1167,8 +1172,7 @@ receipt. | |||
|
|||
The payload and length of the stream are selected in any manner the | |||
implementation chooses. Implementations MAY terminate these streams cleanly, or | |||
MAY abruptly terminate them. When terminating abruptly, the error code | |||
H3_NO_ERROR or a reserved error code ({{http-error-codes}}) SHOULD be used. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the rationale for removing this sentence?
Those that didn't seem to warrant separate issues, anyway.