From: Rich Bowen The HTTP protocol contains built in support for an in-line caching
mechanism
-
- described by section 13 of RFC2616, and the
+ RFC 2616, and the
Full details of how HTTP caching works can be found in
-
- Section 13 of RFC2616.mod_cache
is aimed at both simple and complex caching configurations, where
you are dealing with proxied content, dynamic local content or
@@ -104,8 +103,7 @@
mod_cache module can be used to take advantage of
this.
The full definition of which responses can be cached by an HTTP cache is defined in - - RFC2616 Section 13.4 Response Cacheability, and can be summed up as + RFC 2616 (Response Cacheability), and can be summed up as follows:
The CGI specification defines a number of environment +
The CGI specification (RFC 3875) defines a number of environment variables that expand on those defined by the HTTP spec. These have been adopted more broadly, and are a standard part of passing information between the browser and the diff --git a/docs/manual/env.xml.fr b/docs/manual/env.xml.fr index c3bc568f09..d9fb117187 100644 --- a/docs/manual/env.xml.fr +++ b/docs/manual/env.xml.fr @@ -1,7 +1,7 @@ - + diff --git a/docs/manual/env.xml.ja b/docs/manual/env.xml.ja index ed1672f833..5e5e22f867 100644 --- a/docs/manual/env.xml.ja +++ b/docs/manual/env.xml.ja @@ -1,7 +1,7 @@ - + + + + - + + + + + diff --git a/docs/manual/howto/cgi.xml.fr b/docs/manual/howto/cgi.xml.fr index db28bd39c6..532199c018 100644 --- a/docs/manual/howto/cgi.xml.fr +++ b/docs/manual/howto/cgi.xml.fr @@ -1,7 +1,7 @@ - + diff --git a/docs/manual/howto/cgi.xml.ja b/docs/manual/howto/cgi.xml.ja index 4a9c2fece6..bfa687f378 100644 --- a/docs/manual/howto/cgi.xml.ja +++ b/docs/manual/howto/cgi.xml.ja @@ -1,7 +1,7 @@ - + + + + diff --git a/docs/manual/logs.html.en.utf8 b/docs/manual/logs.html.en.utf8 index 6327c1a54b..89a8da567a 100644 --- a/docs/manual/logs.html.en.utf8 +++ b/docs/manual/logs.html.en.utf8 @@ -345,8 +345,7 @@ CustomLog "logs/access_log" common beginning in 2), a redirection (codes beginning in 3), an error caused by the client (codes beginning in 4), or an error in the server (codes beginning in 5). The full list of - possible status codes can be found in the HTTP - specification (RFC2616 section 10). + possible status codes can be found in the HTTP specification (RFC 2616) (RFC2616 section 10).
2326 (%b)The HTTP/1.1 - RFC, section 14.11 puts it this way:
+The HTTP/1.1 RFC (RFC 2616), 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_mime.xml.fr b/docs/manual/mod/mod_mime.xml.fr index da7ea7828c..2929cf4051 100644 --- a/docs/manual/mod/mod_mime.xml.fr +++ b/docs/manual/mod/mod_mime.xml.fr @@ -1,7 +1,7 @@ - + + + diff --git a/docs/manual/mod/mod_proxy.html.en.utf8 b/docs/manual/mod/mod_proxy.html.en.utf8 index 2366ce25d1..66eea5747e 100644 --- a/docs/manual/mod/mod_proxy.html.en.utf8 +++ b/docs/manual/mod/mod_proxy.html.en.utf8 @@ -1442,7 +1442,7 @@ ProxyPass "/mirror/foo" "http://backend.example.com"
Protocol accepted by
mod_proxy_httpormod_proxy_wstunnelfor the HTTP Upgrade mechanism upon negotiation by the HTTP client/browser (per - RFC 9110 - Upgrade). + RFC 9110 - Upgrade). See the Protocol Upgrade note belowmapping diff --git a/docs/manual/mod/mod_proxy.xml.fr b/docs/manual/mod/mod_proxy.xml.fr index d58a2ed2ba..24b2082387 100644 --- a/docs/manual/mod/mod_proxy.xml.fr +++ b/docs/manual/mod/mod_proxy.xml.fr @@ -1,7 +1,7 @@ - + diff --git a/docs/manual/mod/mod_proxy.xml.ja b/docs/manual/mod/mod_proxy.xml.ja index 458c54db3b..4dcbc0f85d 100644 --- a/docs/manual/mod/mod_proxy.xml.ja +++ b/docs/manual/mod/mod_proxy.xml.ja @@ -1,7 +1,7 @@ - + + + diff --git a/docs/manual/mod/mod_ssl.html.en.utf8 b/docs/manual/mod/mod_ssl.html.en.utf8 index f6ce12222b..99d6de82f8 100644 --- a/docs/manual/mod/mod_ssl.html.en.utf8 +++ b/docs/manual/mod/mod_ssl.html.en.utf8 @@ -725,7 +725,7 @@ key is encrypted, the pass phrase dialog is forced at startup time.As an alternative to storing certificates and private keys in files, a certificate identifier can be used to identify a certificate -stored in a token. Currently, only PKCS#11 URIs are +stored in a token. Currently, only PKCS#11 URIs (RFC 7512) are recognized as certificate identifiers, and can be used in conjunction with the OpenSSL
pkcs11engine or provider. IfSSLCertificateKeyFileis omitted, the certificate and private key can be loaded through the single @@ -819,7 +819,7 @@ key file.As an alternative to storing private keys in files, a key identifier can be used to identify a private key stored in a -token. Currently, only PKCS#11 URIs are recognized as private key +token. Currently, only PKCS#11 URIs (RFC 7512) are recognized as private key identifiers, and can be used in conjunction with the OpenSSL
@@ -1083,11 +1083,11 @@ SSLCryptoDevice ubsecpkcs11engine or provider.With OpenSSL 3.0 or later, if no engine is specified but the key or certificate -is specified using a PKCS#11 URIs +is specified using a PKCS#11 URIs (RFC 7512) then it is tried to load the key and certificate from an OpenSSL provider. The OpenSSL provider to use must be defined and configured in the OpenSSL config file, and it must support the STORE method -for PKCS#11 URIs. +for PKCS#11 URIs (RFC 7512).
@@ -1104,7 +1104,7 @@ for PKCS#11 URIs.ECH is specified in - draft-ietf-tls-esni + RFC 9849 httpd supports ECH "shared-mode" where the httpd instance does the ECH decryption and also hosts both the ECH `public-name` and `backend` web sites. diff --git a/docs/manual/mod/mod_ssl.xml.es b/docs/manual/mod/mod_ssl.xml.es index 88bcffce5d..135a501d1b 100644 --- a/docs/manual/mod/mod_ssl.xml.es +++ b/docs/manual/mod/mod_ssl.xml.es @@ -1,7 +1,7 @@ - + diff --git a/docs/manual/mod/mod_ssl.xml.fr b/docs/manual/mod/mod_ssl.xml.fr index 9f151317db..62de9c2aee 100644 --- a/docs/manual/mod/mod_ssl.xml.fr +++ b/docs/manual/mod/mod_ssl.xml.fr @@ -1,7 +1,7 @@ - + diff --git a/docs/manual/new_features_2_6.html.en.utf8 b/docs/manual/new_features_2_6.html.en.utf8 index fd60a31268..a8e0fd83b1 100644 --- a/docs/manual/new_features_2_6.html.en.utf8 +++ b/docs/manual/new_features_2_6.html.en.utf8 @@ -47,7 +47,7 @@
- The
diff --git a/docs/manual/programs/htdigest.html.en.utf8 b/docs/manual/programs/htdigest.html.en.utf8 index e3543845f8..ac86cdba5d 100644 --- a/docs/manual/programs/htdigest.html.en.utf8 +++ b/docs/manual/programs/htdigest.html.en.utf8 @@ -64,8 +64,7 @@ContentDigestdirective and support for the theContent-MD5header has been removed from the server, corresponding with the removal of this header from - + RFC7231 Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content.realm- The realm name to which the user name belongs. See - - http://tools.ietf.org/html/rfc2617#section-3.2.1 for more details. + RFC 2617 for more details.
- diff --git a/docs/manual/programs/htdigest.xml.fr b/docs/manual/programs/htdigest.xml.fr index 1f1131fae9..05b8da720b 100644 --- a/docs/manual/programs/htdigest.xml.fr +++ b/docs/manual/programs/htdigest.xml.fr @@ -1,7 +1,7 @@ - + diff --git a/docs/manual/programs/htdigest.xml.ko b/docs/manual/programs/htdigest.xml.ko index d6bef34f50..ef38d55084 100644 --- a/docs/manual/programs/htdigest.xml.ko +++ b/docs/manual/programs/htdigest.xml.ko @@ -1,7 +1,7 @@ - + + + diff --git a/docs/manual/ssl/ssl_intro.xml.ja b/docs/manual/ssl/ssl_intro.xml.ja index 9cad0b34cb..beaef94a8b 100644 --- a/docs/manual/ssl/ssl_intro.xml.ja +++ b/docs/manual/ssl/ssl_intro.xml.ja @@ -1,7 +1,7 @@ - +
username