You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by rb...@apache.org on 2026/05/03 16:00:48 UTC

svn commit: r1933771 - httpd/httpd/branches/2.4.x/docs/manual/mod

Author: rbowen
Date: Sun May  3 16:00:48 2026
New Revision: 1933771

Log:
core: Note that http/1.1 cannot be excluded via Protocols directive (Bug 62543)

Modified:
   httpd/httpd/branches/2.4.x/docs/manual/mod/core.xml

Modified: httpd/httpd/branches/2.4.x/docs/manual/mod/core.xml
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/mod/core.xml	Sun May  3 16:00:45 2026	(r1933770)
+++ httpd/httpd/branches/2.4.x/docs/manual/mod/core.xml	Sun May  3 16:00:48 2026	(r1933771)
@@ -4126,6 +4126,14 @@ Protocols h2 http/1.1
         <p>It is safe to specify protocols that are unavailable/disabled. Such
         protocol names will simply be ignored.</p>
         
+        <note><title>Note</title>
+        <p>The <code>http/1.1</code> protocol is always available and
+            cannot be excluded by omitting it from this directive.
+            This directive controls which additional protocols are
+            available for negotiation, and, when used with
+            <directive>ProtocolsHonorOrder</directive>, their preference
+            order.</p></note>
+
         <p>Protocols specified in base servers are inherited for virtual hosts 
             only if the virtual host has no own Protocols directive. Or, the other
             way around, Protocols directives in virtual hosts replace any