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

update refs for -12 of http core drafts #4182

Merged
merged 3 commits into from Oct 16, 2020
Merged

update refs for -12 of http core drafts #4182

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8809c39
update refs for -12 of http core drafts
reschke Oct 4, 2020
ec98681
Apply suggestions from code review
MikeBishop Oct 16, 2020
44492f7
Rewrap
MikeBishop Oct 16, 2020
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
8 changes: 4 additions & 4 deletions draft-ietf-quic-http.md
View file
Open in desktop
Expand Up @@ -1774,10 +1774,10 @@ attack on a plaintext protocol.
## Intermediary Encapsulation Attacks

The HTTP/3 field encoding allows the expression of names that are not valid
field names in the syntax used by HTTP (Section 5.4.3 of {{!SEMANTICS}}). Requests
or responses containing invalid field names MUST be treated as malformed
({{malformed}}). An intermediary therefore cannot translate an HTTP/3 request
or response containing an invalid field name into an HTTP/1.1 message.
field names in the syntax used by HTTP (Section 5.4.3 of {{!SEMANTICS}}).
Requests or responses containing invalid field names MUST be treated as
malformed ({{malformed}}). An intermediary therefore cannot translate an HTTP/3
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,
Expand Down