From 5bb003ed37ac97ad12c12a2bce78cf0501666c41 Mon Sep 17 00:00:00 2001
From: Euclid Ye <euclid.ye@huawei.com>
Date: Fri, 15 May 2026 13:26:51 +0800
Subject: [PATCH] clarify multipart/form-data field name escaping ambiguity

Signed-off-by: Euclid Ye <yezhizhenjiakang@gmail.com>
---
 source | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/source b/source
index 291c45fff57..1facba783ec 100644
--- a/source
+++ b/source
@@ -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>