content-encoding always available

Author: guohuideng2024

fetch.bs

@@ -5042,10 +5042,11 @@ steps:
      <li><p>Let <var>type</var> be <var>blob</var>'s {{Blob/type}}.
 
      <li><p>Let <var>accept-coding</var> be the result of <a for="header list">getting</a>
-       `<code>Content-Encoding</code>` from <var>request</var>'s <a for=request>header list</a>.
+       `<code>Accept-Encoding</code>` from <var>request</var>'s <a for=request>header list</a>.
         If <var>accept-encoding</var> is not null and the server selects one of the encoding options,
-        let <var>coding</var> be the selected encoding option; otherwise, i.e., let <var>coding</var>
-        be null.
+        let <var>coding</var> be the selected encoding option; otherwise, i.e., no encoding is used,
+        let <var>coding</var> be <a href=https://httpwg.org/specs/rfc9110.html#field.accept-encoding>
+        <code>"identity"</code></a>.
 
      <li>
       <p>If <var>request</var>'s <a for=request>header list</a>
@@ -5062,10 +5063,8 @@ steps:
 
        <li><p>Set <var>response</var>'s <a for=response>header list</a> to «
        (`<code>Content-Length</code>`, <var>serializedFullLength</var>),
-       (`<code>Content-Type</code>`, <var>type</var>) ».
-
-       <li><p>If <var>coding</var> is non-null,<a for="header list"> append</a> (`<code>Content-Encoding</code>`,
-        <var>coding</var>) to <var>response</var>'s <a for=response>header list</a>.
+       (`<code>Content-Type</code>`, <var>type</var>),
+       (`<code>Content-Encoding</code>`, <var>coding</var>) ».
 
       </ol>
 
@@ -5135,10 +5134,8 @@ steps:
        <li><p>Set <var>response</var>'s <a for=response>header list</a> to «
        (`<code>Content-Length</code>`, <var>serializedSlicedLength</var>),
        (`<code>Content-Type</code>`, <var>type</var>), (`<code>Content-Range</code>`,
-       <var>contentRange</var>) ».
+       <var>contentRange</var>), (`<code>Content-Encoding</code>`, <var>coding</var>) ».
 
-       <li><p>If <var>coding</var> is non-null,<a for="header list"> append</a> (`<code>Content-Encoding</code>`,
-        <var>coding</var>) to <var>response</var>'s <a for=response>header list</a>.
       </ol>
 
      <li><p>Return <var>response</var>.
@@ -5156,26 +5153,17 @@ steps:
      <a for="data: URL struct">MIME type</a>, <a lt="serialize a MIME type to bytes">serialized</a>.
 
      <li><p>Let <var>accept-coding</var> be the result of <a for="header list">getting</a>
-       `<code>Content-Encoding</code>` from <var>request</var>'s <a for=request>header list</a>.
+       `<code>Accept-Encoding</code>` from <var>request</var>'s <a for=request>header list</a>.
         If <var>accept-encoding</var> is not null and the server selects one of the encoding options,
-        let <var>coding</var> be the selected encoding option; otherwise, i.e., let <var>coding</var>
-        be null.
-     <li><p>Let <var>response</var> be a new <a for=/>response</a>.
-
-     <li><p>Set <var>response</var>'s <a for=response>status message</a> to
-     <code>OK</code>`.
-
-     <li><p>Set <var>response</var>'s <a for=response>header list</a> to «
-     (`<code>Content-Type</code>`, <var>mimeType</var>)».
-
-     <li><p>If <var>coding</var> is non-null,<a for="header list"> append</a>
-     (`<code>Content-Encoding</code>`, <var>coding</var>) to <var>response</var>'s
-     <a for=response>header list</a>.
-
-     <li><p>Set <var>response</var>'s <a for=response>body</a> to <var>dataURLStruct</var>'s
-     <a for="data: URL struct">body</a>
-
-     <li><p>Return <var>response</var>.
+        let <var>coding</var> be the selected encoding option; otherwise, i.e., no encoding is used,
+        let <var>coding</var> be <a href=https://httpwg.org/specs/rfc9110.html#field.accept-encoding>
+        <code>"identity"</code></a>.
+
+     <li><p>Return a new <a for=/>response</a> whose <a for=response>status message</a> is
+     `<code>OK</code>`, <a for=response>header list</a> is « (`<code>Content-Type</code>`,
+     <var>mimeType</var>), (`<code>Content-Encoding</code>`, <var>coding</var>) », and
+     <a for=response>body</a> is <var>dataURLStruct</var>'s <a for="data: URL struct">
+     body</a> <a for="byte sequence">as a body</a>.
 
     </ol>