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

Malformed could get its own error #4346

Merged
merged 3 commits into from Dec 14, 2020
Merged
Changes from 2 commits
Commits
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
7 changes: 4 additions & 3 deletions draft-ietf-quic-http.md
Expand Up @@ -733,7 +733,7 @@ frames but is invalid due to:
- pseudo-header fields after fields,
- an invalid sequence of HTTP messages,
- the inclusion of uppercase field names, or
- the inclusion of invalid characters in field names or values
- the inclusion of invalid characters in field names or values.

A request or response that includes a payload body can include a
Content-Length header field. A request or response is also malformed if the
Expand Down Expand Up @@ -2447,8 +2447,9 @@ NO_ERROR (0x0):

PROTOCOL_ERROR (0x1):
: This is mapped to H3_GENERAL_PROTOCOL_ERROR except in cases where more
specific error codes have been defined. Such cases include H3_FRAME_UNEXPECTED
and H3_CLOSED_CRITICAL_STREAM defined in {{http-error-codes}}.
specific error codes have been defined. Such cases include
H3_FRAME_UNEXPECTED, H3_MESSAGE_ERROR, and H3_CLOSED_CRITICAL_STREAM defined
in {{http-error-codes}}.

INTERNAL_ERROR (0x2):
: H3_INTERNAL_ERROR in {{http-error-codes}}.
Expand Down