Skip to content

Editorial: Clarify multipart/form-data field name escaping ambiguity #12459

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

Open
yezhizhen wants to merge 1 commit into
base: main
Choose a base branch
from
+1 −1
Open

Editorial: Clarify multipart/form-data field name escaping ambiguity #12459

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.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion source
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64742,7 +64742,7 @@ fur
data-x="encode">encoding</span> the corresponding entry's name or value with
<var>encoding</var>, converted to a byte sequence.</p></li>

<li><p>For field names and filenames for file fields, the result of the encoding in the
<li><p>For all field names, as well as filenames for file fields, the result of the encoding in the
previous bullet point must be escaped by replacing any 0x0A (LF) bytes with the byte sequence
`<code data-x="">%0A</code>`, 0x0D (CR) with `<code data-x="">%0D</code>` and 0x22 (") with
`<code data-x="">%22</code>`. The user agent must not perform any other escapes.</p></li>
Expand Down