From eb24addc23e51948d1912837878a192de222a5b5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bence=20B=C3=A9ky?= Date: Mon, 13 Sep 2021 11:14:11 -0400 Subject: [PATCH] [http] [editorial] Fix ASCII code for LF, NUL. --- draft-ietf-quic-http.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/draft-ietf-quic-http.md b/draft-ietf-quic-http.md index 2a6b0d3999..03a59e70d5 100644 --- a/draft-ietf-quic-http.md +++ b/draft-ietf-quic-http.md @@ -1826,8 +1826,8 @@ request or response containing an invalid field name into an HTTP/1.1 message. Similarly, HTTP/3 can transport field values that are not valid. While most values that can be encoded will not alter field parsing, carriage return (CR, -ASCII 0x0d), line feed (LF, ASCII 0x0d), and the zero character (NUL, ASCII -0x0d) might be exploited by an attacker if they are translated verbatim. Any +ASCII 0x0d), line feed (LF, ASCII 0x0a), and the zero character (NUL, ASCII +0x00) might be exploited by an attacker if they are translated verbatim. Any request or response that contains a character not permitted in a field value MUST be treated as malformed ({{malformed}}). Valid characters are defined by the "field-content" ABNF rule in {{Section 5.5 of SEMANTICS}}.