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

Specify behavior on incomplete requests #1643

Merged
merged 6 commits into from Aug 14, 2018
Merged

Specify behavior on incomplete requests #1643

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
bbda80c
HTTP_EARLY_RESPONSE not defined (Whoops\!)
MikeBishop Aug 8, 2018
24bbe71
Define HTTP_INCOMPLETE_REQUEST
MikeBishop Aug 8, 2018
a9c73a0
Recommend bidirectional cancellation for clients
MikeBishop Aug 8, 2018
482badb
More separated
MikeBishop Aug 9, 2018
c777723
Usable
MikeBishop Aug 10, 2018
59da706
(that too)
MikeBishop Aug 10, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
10 changes: 5 additions & 5 deletions draft-ietf-quic-http.md
View file
Open in desktop
Expand Up @@ -320,11 +320,11 @@ and cleanly closing its streams. Clients MUST NOT discard complete responses as
a result of having their request terminated abruptly, though clients can always
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.
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
Changes to the state of a request stream, including receiving a RST_STREAM with
any error code, do not affect the state of the server's response. 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