From: Rich Bowen <rbowen@apache.org>
Date: Tue, 5 May 2026 17:19:37 +0000 (+0000)
Subject: docs: Add anchor attr to <rfc> tag, convert remaining RFC fragment links, fix http... 
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=86afe6df10654c674f1aae38c712e21c3b25b29e;p=thirdparty%2Fapache%2Fhttpd.git

docs: Add anchor attr to <rfc> tag, convert remaining RFC fragment links, fix http->https

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1933854 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/docs/manual/misc/relevant_standards.xml b/docs/manual/misc/relevant_standards.xml
index 05d1bc9e18..3cfd3afe11 100644
--- a/docs/manual/misc/relevant_standards.xml
+++ b/docs/manual/misc/relevant_standards.xml
@@ -38,8 +38,8 @@
         https://www.skrb.org/ietf/http_errata.html</a> - HTTP/1.1 Specification Errata
       </li>
       <li>
-        <a href="http://www.rfc-editor.org/errata.php">
-        http://www.rfc-editor.org/errata.php</a> - RFC Errata
+        <a href="https://www.rfc-editor.org/errata.php">
+        https://www.rfc-editor.org/errata.php</a> - RFC Errata
       </li>
       <li>
         <a href="https://httpwg.org/specs/">
@@ -175,7 +175,7 @@
       in English) in alphabetical order as given in ISO 3166-1 and the
       corresponding ISO 3166-1-alpha-2 code elements.</dd>
 
-      <dt><a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">BCP 47</a>
+      <dt><a href="https://www.rfc-editor.org/rfc/bcp/bcp47.txt">BCP 47</a>
       (Best Current Practice),
       <rfc>3066</rfc></dt>
 
diff --git a/docs/manual/mod/core.xml b/docs/manual/mod/core.xml
index 555f009e81..ed22cf463f 100644
--- a/docs/manual/mod/core.xml
+++ b/docs/manual/mod/core.xml
@@ -1389,9 +1389,8 @@ EnableSendfile On
       <p><rfc section="19.6">2616</rfc> "Compatibility With Previous Versions" had
       encouraged HTTP servers to support legacy HTTP/0.9 requests. RFC 7230
       supersedes this with "The expectation to support HTTP/0.9 requests has
-      been removed" and offers additional comments in 
-      <a href="https://www.rfc-editor.org/rfc/rfc7230#appendix-A"
-        >RFC 7230 Appendix A</a>. The <code>Require1.0</code> option allows
+      been removed" and offers additional comments in
+      <rfc anchor="appendix-A">7230</rfc> Appendix A. The <code>Require1.0</code> option allows
       the user to remove support of the default <code>Allow0.9</code> option's
       behavior.</p>
 
diff --git a/docs/manual/mod/mod_mime_magic.xml b/docs/manual/mod/mod_mime_magic.xml
index 0fa9b47f3e..311096d0fd 100644
--- a/docs/manual/mod/mod_mime_magic.xml
+++ b/docs/manual/mod/mod_mime_magic.xml
@@ -294,7 +294,7 @@ using the specified magic file</description>
     <li><strong>Not RFC-compliant:</strong> Standards documents consistently
     recommend against setting Content-Encoding for files that are already
     compressed (such as .zip or .gz files). See
-    <a href="https://www.rfc-editor.org/rfc/rfc9110#name-content-encoding">RFC 9110</a>.</li>
+    <rfc anchor="name-content-encoding">9110</rfc>.</li>
 
     <li><strong>Breaks content integrity:</strong> When Content-Encoding is set,
     most HTTP clients will decompress the file before writing it to disk. This
diff --git a/docs/manual/mod/mod_proxy.xml b/docs/manual/mod/mod_proxy.xml
index 3d711b374d..1f51a2c894 100644
--- a/docs/manual/mod/mod_proxy.xml
+++ b/docs/manual/mod/mod_proxy.xml
@@ -1320,7 +1320,7 @@ ProxyPass "/example" "http://backend.example.com" max=20 ttl=120 retry=300
         <td><p>Protocol accepted by <module>mod_proxy_http</module> or
         <module>mod_proxy_wstunnel</module> for the HTTP Upgrade mechanism
         upon negotiation by the HTTP client/browser (per
-        <a href="https://www.rfc-editor.org/rfc/rfc9110#name-upgrade">RFC 9110 - Upgrade</a>).
+        <rfc anchor="name-upgrade">9110</rfc> - Upgrade).
         See the <a href="#protoupgrade">Protocol Upgrade</a> note below</p>
     </td></tr>
     <tr><td>mapping</td>
diff --git a/docs/manual/new_features_2_6.xml b/docs/manual/new_features_2_6.xml
index 55ac276365..d11c6251bc 100644
--- a/docs/manual/new_features_2_6.xml
+++ b/docs/manual/new_features_2_6.xml
@@ -38,9 +38,8 @@
       <dd>The <code>ContentDigest</code> directive and support for the the
           <code>Content-MD5</code> header has been removed from the server,
           corresponding with the removal of this header from
-          <a href="https://www.rfc-editor.org/rfc/rfc7231#appendix-B">
-          RFC7231 Hypertext Transfer Protocol (HTTP/1.1): Semantics and
-          Content.</a></dd>
+          <rfc anchor="appendix-B">7231</rfc> Hypertext Transfer Protocol
+          (HTTP/1.1): Semantics and Content.</dd>
 
       <dt><code>Listen</code> directive options</dt>
       <dd>The <directive module="mpm_common">Listen</directive>
diff --git a/docs/manual/style/common.dtd b/docs/manual/style/common.dtd
index 08ead9d3c0..67128a349d 100644
--- a/docs/manual/style/common.dtd
+++ b/docs/manual/style/common.dtd
@@ -203,7 +203,9 @@ highlight | blockquote">
 
 <!-- The rfc element creates a link to an RFC at www.rfc-editor.org.
      Content is the RFC number (e.g. 7230). Optional section attribute
-     adds a fragment anchor (e.g. section="14.24"). -->
+     adds a fragment anchor (e.g. section="14.24"). Optional anchor attribute
+     adds a raw fragment (e.g. anchor="appendix-B", anchor="name-upgrade"). -->
 <!ELEMENT rfc (#PCDATA)>
-<!ATTLIST rfc section CDATA #IMPLIED>
+<!ATTLIST rfc section CDATA #IMPLIED
+              anchor  CDATA #IMPLIED>
 
diff --git a/docs/manual/style/xsl/common.xsl b/docs/manual/style/xsl/common.xsl
index 513846a311..8cf6122d08 100644
--- a/docs/manual/style/xsl/common.xsl
+++ b/docs/manual/style/xsl/common.xsl
@@ -1242,6 +1242,10 @@ if (typeof(prettyPrint) !== 'undefined') {
       <xsl:text>#section-</xsl:text>
       <xsl:value-of select="@section"/>
     </xsl:if>
+    <xsl:if test="@anchor">
+      <xsl:text>#</xsl:text>
+      <xsl:value-of select="@anchor"/>
+    </xsl:if>
   </xsl:variable>
 
   <a href="{$rfcurl}">RFC <xsl:value-of select="$rfcnum"/></a>