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/">
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>
<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>
<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
<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>
<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>
<!-- 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>
<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>