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

Specify behavior on incomplete requests #1643

Merged
merged 6 commits into from
Aug 14, 2018
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions draft-ietf-quic-http.md
Original file line number Diff line number Diff line change
Expand Up @@ -322,10 +322,10 @@ discard responses at their discretion for other reasons.

Changes to the state of a request stream, including receiving a RST_STREAM
(regardless of error code), do not affect the state of the server's response.
Copy link
Member

Choose a reason for hiding this comment

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

s/(regardless of error code)/with any error code/

Servers MUST NOT abort a response in progress solely due to a state change on
the request stream. However, if the request stream terminates without containing
a fully-formed HTTP request, the server SHOULD abort its response with the error
code HTTP_INCOMPLETE_REQUEST.
Servers do not abort a response in progress solely due to a state change on the
request stream. However, if the request stream terminates without containing a
usable HTTP request, the server SHOULD abort its response with the error code
HTTP_INCOMPLETE_REQUEST.

### Header Formatting and Compression

Expand Down