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

Application can reset stream or close connection even if no error occurs. #3953

Merged
merged 5 commits into from
Aug 10, 2020
Merged
Changes from all commits
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: 5 additions & 3 deletions draft-ietf-quic-http.md
Original file line number Diff line number Diff line change
Expand Up @@ -1595,9 +1595,11 @@ sent, and receipt MAY be treated as an error of type H3_FRAME_UNEXPECTED.
# Error Handling {#errors}

QUIC allows the application to abruptly terminate (reset) individual streams or
the entire connection when an error is encountered. These are referred to as
"stream errors" or "connection errors" and are described in more detail in
{{QUIC-TRANSPORT}}.
the entire connection; see Sections 2.4 and 5.3 of {{QUIC-TRANSPORT}}. These
are referred to as "stream errors" or "connection errors" (see Section 11 of
{{QUIC-TRANSPORT}}) and have associated error codes, but do not necessarily
indicate a problem with the connection or either implementation. For example, a
stream can be reset if the requested resource is no longer needed.

An endpoint MAY choose to treat a stream error as a connection error under
certain circumstances. Implementations need to consider the impact on
Expand Down