From: Joe Orton Date: Fri, 4 Apr 2025 16:18:31 +0000 (+0000) Subject: Update to use rfc-editor.org URLs throughout. X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=2738357b817d214d23365326adadadbb5f6e20d5;p=thirdparty%2Fapache%2Fhttpd.git Update to use rfc-editor.org URLs throughout. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1924775 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_autht_jwt.xml b/docs/manual/mod/mod_autht_jwt.xml index 08c49ba8bc..87815d4086 100644 --- a/docs/manual/mod/mod_autht_jwt.xml +++ b/docs/manual/mod/mod_autht_jwt.xml @@ -32,7 +32,7 @@

This module provides token parsing front-ends such as mod_auth_bearer the ability to authenticate users by verifying a JWT token as described in - RFC 7519.

+ RFC 7519.

A JWT token is read from the Authorization header with an auth-scheme of Bearer.

diff --git a/docs/manual/mod/mod_cache.xml b/docs/manual/mod/mod_cache.xml index 5c1f5134de..23471d828a 100644 --- a/docs/manual/mod/mod_cache.xml +++ b/docs/manual/mod/mod_cache.xml @@ -39,7 +39,7 @@ variable.

mod_cache implements an RFC 2616 compliant + href="https://www.rfc-editor.org/rfc/rfc2616">RFC 2616 compliant HTTP content caching filter, with support for the caching of content negotiated responses containing the Vary header.

diff --git a/docs/manual/mod/mod_ident.xml b/docs/manual/mod/mod_ident.xml index 82b33218e1..7bc4551612 100644 --- a/docs/manual/mod/mod_ident.xml +++ b/docs/manual/mod/mod_ident.xml @@ -29,7 +29,7 @@ ident_module -

This module queries an This module queries an RFC 1413 compatible daemon on a remote host to look up the owner of a connection.

 @@ -45,7 +45,7 @@ user directory -

This directive enables This directive enables RFC 1413-compliant logging of the remote user name for each connection, where the client machine runs identd or something similar. This information is logged in the access log using the %...l @@ -77,7 +77,7 @@ user

This directive specifies the timeout duration of an ident request. The default value of 30 seconds is recommended by RFC 1413, mainly because + href="https://www.rfc-editor.org/rfc/rfc1413">RFC 1413, mainly because of possible network latency. However, you may want to adjust the timeout value according to your local network speed.

 diff --git a/docs/manual/mod/mod_mime.xml b/docs/manual/mod/mod_mime.xml index c73b953d1a..f774d3b562 100644 --- a/docs/manual/mod/mod_mime.xml +++ b/docs/manual/mod/mod_mime.xml @@ -161,10 +161,10 @@ module="mod_mime_magic">MimeMagicFile designed for transmitting a binary file in an ASCII (text) format.

-

The HTTP/1.1 +

The HTTP/1.1 RFC, section 14.11 puts it this way:

-
+

The Content-Encoding entity-header field is used as a modifier to the media-type. When present, its value indicates what additional content codings have been applied to the entity-body, and thus what diff --git a/docs/manual/mod/mod_negotiation.xml b/docs/manual/mod/mod_negotiation.xml index 97a11b04b0..d5f0c3f308 100644 --- a/docs/manual/mod/mod_negotiation.xml +++ b/docs/manual/mod/mod_negotiation.xml @@ -76,7 +76,7 @@ Negotiation

Content-Language:
The language(s) of the variant, as an Internet standard - language tag (RFC 1766). An example is en, meaning English. If the variant contains more than one language, they are separated by a comma.
diff --git a/docs/manual/mod/mod_proxy.xml b/docs/manual/mod/mod_proxy.xml index 4a44ad5bb9..4205b86c13 100644 --- a/docs/manual/mod/mod_proxy.xml +++ b/docs/manual/mod/mod_proxy.xml @@ -2087,7 +2087,7 @@ header for proxied requests

This directive controls the use of the Via: HTTP header by the proxy. Its intended use is to control the flow of proxy requests along a chain of proxy servers. See RFC 2616 (HTTP/1.1), section + href="https://www.rfc-editor.org/rfc/rfc2616">RFC 2616 (HTTP/1.1), section 14.45 for an explanation of Via: header lines.

    diff --git a/docs/manual/mod/mod_ssl.xml b/docs/manual/mod/mod_ssl.xml index 4cc50c1ff4..cbe9d67de8 100644 --- a/docs/manual/mod/mod_ssl.xml +++ b/docs/manual/mod/mod_ssl.xml @@ -601,7 +601,7 @@ SSLEngine on

    SSLEngine can be set to optional: this enables support for -RFC 2817. +RFC 2817.

    @@ -653,29 +653,29 @@ The available (case-insensitive) protocols are:

    This is the Secure Sockets Layer (SSL) protocol, version 3.0, from the Netscape Corporation. It is the successor to SSLv2 and the predecessor to TLSv1, but is - deprecated in RFC 7568.

    + deprecated in RFC 7568.

  • TLSv1

    This is the Transport Layer Security (TLS) protocol, version 1.0. It is the successor to SSLv3 and is defined in - RFC 2246. + RFC 2246. It is supported by nearly every client.

  • TLSv1.1 (when using OpenSSL 1.0.1 and later)

    A revision of the TLS 1.0 protocol, as defined in - RFC 4346.

    • + RFC 4346.

  • TLSv1.2 (when using OpenSSL 1.0.1 and later)

    A revision of the TLS 1.1 protocol, as defined in - RFC 5246.

    • + RFC 5246.

  • TLSv1.3 (when using OpenSSL 1.1.1 and later)

    A new version of the TLS protocol, as defined in - RFC 8446.

    • + RFC 8446.

  • all

    @@ -981,7 +981,7 @@ Beginning with version 2.4.7, mod_ssl makes use of standardized DH parameters with prime lengths of 2048, 3072 and 4096 bits and with additional prime lengths of 6144 and 8192 bits beginning with version 2.4.10 -(from RFC 3526), and hands +(from RFC 3526), and hands them out to clients based on the length of the certificate's RSA/DSA key. With Java-based clients in particular (Java 7 or earlier), this may lead to handshake failures - see this @@ -2660,7 +2660,7 @@ OCSP response for a single cert. For server certificates with intermediate CA certificates in their chain (the typical case nowadays), stapling in its current implementation therefore only partially achieves the stated goal of "saving roundtrips and resources" - see also -RFC 6961 +RFC 6961 (TLS Multiple Certificate Status Extension).

    @@ -2843,7 +2843,7 @@ One potential use is when a proxy is used for retrieving OCSP queries.

    Optionally configures a secret key for encrypting and decrypting TLS session tickets, as defined in -RFC 5077. +RFC 5077. Primarily suitable for clustered environments where TLS sessions information should be shared between multiple nodes. For single-instance httpd setups, it is recommended to not configure a ticket key file, but to