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

HTTP: Tweak wording about unknown error codes #3239

Closed
wants to merge 1 commit into from
Closed

HTTP: Tweak wording about unknown error codes #3239

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion draft-ietf-quic-http.md
View file
Open in desktop
Expand Up @@ -1384,7 +1384,7 @@ connection error.

Because new error codes can be defined without negotiation (see {{extensions}}),
receipt of an unknown error code or use of an error code in an unexpected
context MUST NOT be treated as an error. However, closing a stream can
context MUST NOT be treated as a further error. However, closing a stream can
Copy link
Member

Choose a reason for hiding this comment

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

Maybe: receipt of an unknown error code or use of an error code in an unexpected context MUST NOT be treated as a connection error.

Suggested change
context MUST NOT be treated as a further error. However, closing a stream can
context MUST NOT be treated as a connection error. However, closing a stream can

constitute an error regardless of the error code (see {{request-response}}).

This section describes HTTP/3-specific error codes which can be used to express
Expand Down