[fetch] Meta: reference new Structured Field Values RFC whatwg/fetch@1dc1b03

Author: triple-underscore

Fetch-ja.html

@@ -207,7 +207,7 @@
 ●●options
 
 spec_title:Fetch
-spec_date:2024-10-01
+spec_date:2024-10-24
 trans_update:2024-10-01
 source_checked:231107
 spec_status:LS
@@ -2317,10 +2317,10 @@
     P. Kyzivat. ＜Case-Sensitive String Support in ABNF＞. December 2014. Proposed Standard. URL: https://www.rfc-editor.org/rfc/rfc7405
 [RFC7578]
     L. Masinter. ＜Returning Values from Forms: multipart/form-data＞. July 2015. Proposed Standard. URL: https://www.rfc-editor.org/rfc/rfc7578
-[RFC8941]
-    M. Nottingham; P-H. Kamp. ＜Structured Field Values for HTTP＞. February 2021. Proposed Standard. URL: https://httpwg.org/specs/rfc8941.html
 [RFC9218]
     K. Oku; L. Pardue. ＜Extensible Prioritization Scheme for HTTP＞. June 2022. Proposed Standard. URL: https://httpwg.org/specs/rfc9218.html
+[RFC9651]
+    M. Nottingham; P-H. Kamp. ＜Structured Field Values for HTTP＞. September 2024. Proposed Standard. URL: https://www.rfc-editor.org/rfc/rfc9651
 [SRI]
     Devdatta Akhawe; et al. ＜Subresource Integrity＞. URL: https://w3c.github.io/webappsec-subresource-integrity/
 [STALE-WHILE-REVALIDATE]
@@ -2390,7 +2390,7 @@
 
 Commits:
 	https://github.com/whatwg/fetch/commits
-	<a href="https://fetch.spec.whatwg.org/commit-snapshots/761c414c2d98c6242d2b3ac478fb8e7558086633/" id="commit-snapshot-link">Snapshot as of this commit</a>
+	<a href="https://fetch.spec.whatwg.org/commit-snapshots/1dc1b034b208faf6652dced19954f67717da9ba1/" id="commit-snapshot-link">Snapshot as of this commit</a>
 	<a href="https://twitter.com/fetchstandard">@fetchstandard</a>
 
 Tests:
@@ -3810,9 +3810,9 @@ <h4 title="Headers">2.2.2. ~header</h4>
 `~header~list$から得するためには，構文解析する他にない。
 将来には、
 それらが~objである事は，端点間で保全されるであろう。
-`RFC8941$r
+`RFC9651$r
 ◎
-Structured field values are defined as objects which HTTP can (eventually) serialize in interesting and efficient ways. For the moment, Fetch only supports header values as byte sequences, which means that these objects can be set in header lists only via serialization, and they can be obtained from header lists only by parsing. In the future the fact that they are objects might be preserved end-to-end. [RFC8941]
+Structured field values are defined as objects which HTTP can (eventually) serialize in interesting and efficient ways. For the moment, Fetch only supports header values as byte sequences, which means that these objects can be set in header lists only via serialization, and they can be obtained from header lists only by parsing. In the future the fact that they are objects might be preserved end-to-end. [RFC9651]
 </p>
 </div>
 
@@ -6868,7 +6868,7 @@ <h3 title="Requests">2.2.5. 要請</h3>
 			<dd>
 これは、
 特別な~modeであり，
-文書~間で`~navigate$するときに限り利用される。
+文書~間で`~navigate$【！~WINDOW#blocking-navigating】するときに限り利用される。
 ◎
 This is a special mode used only when navigating between documents.
 </dd>