Merge pull request #2597 from w3c/editorial/fix-obs-rfc-ref

Replace references to obsolete rfc7230 with rfc9110
w3c · Dec 8, 2023 · 6daf1e3 · 6daf1e3
2 parents 932fe2c + fb8e5c6
commit 6daf1e3
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/epub33/core/index.html b/epub33/core/index.html
@@ -1445,7 +1445,7 @@ <h4>Resource locations</h4>
 					users access to the entire presentation regardless of connectivity status.</p>
 
 				<p>When resources have to be located outside the EPUB container, EPUB creators are RECOMMENDED to
-					reference them via the secure <code>https</code> URI scheme [rfc7230] to limit the threat of
+					reference them via the secure <code>https</code> URI scheme [[rfc9110]] to limit the threat of
 					exposing their publications, and users, to network attacks. [=Reading systems=] might not load
 					[=remote resources=] referenced using insecure schemes such as <code>http</code>.</p>
 

diff --git a/epub33/rs/index.html b/epub33/rs/index.html
@@ -342,7 +342,7 @@ <h4>Resource locations</h4>
 						data-cite="epub-33#sec-resource-locations">Resource locations</a> [[epub-33]].</p>
 
 				<p>To limit the risk of network attacks, reading systems SHOULD only load remote resources referenced
-					via the <code>https</code> URI scheme [[rfc7230]].</p>
+					via the <code>https</code> URI scheme [[rfc9110]].</p>
 			</section>
 
 			<section id="sec-epub-rs-conf-data-urls">