Author: markt
Date: Thu Nov 30 14:24:52 2017
New Revision: 1816716

Document HTTP/2 compression support


Modified: tomcat/trunk/webapps/docs/changelog.xml
--- tomcat/trunk/webapps/docs/changelog.xml (original)
+++ tomcat/trunk/webapps/docs/changelog.xml Thu Nov 30 14:24:52 2017
@@ -55,6 +55,14 @@
+  <subsection>
+    <changelog>
+      <add>
+        <bug>60276</bug>: Implement GZIP compression support for responses
+        served over HTTP/2. (markt)
+      </add>
+    </changelog>
+  </subsection>
   <subsection name="Other">

Modified: tomcat/trunk/webapps/docs/config/http2.xml
--- tomcat/trunk/webapps/docs/config/http2.xml (original)
+++ tomcat/trunk/webapps/docs/config/http2.xml Thu Nov 30 14:24:52 2017
@@ -77,6 +77,46 @@
       comma-separated list of header names.</p>
+    <attribute name="compressibleMimeType" required="false">
+      <p>The value is a comma separated list of MIME types for which HTTP
+      compression may be used.
+      The default value is
+      <code>
+      </code>.
+      </p>
+    </attribute>
+    <attribute name="compression" required="false">
+      <p>The HTTP/2 protocol may use compression in an attempt to save server
+      bandwidth. The acceptable values for the parameter is "off" (disable
+      compression), "on" (allow compression, which causes text data to be
+      compressed), "force" (forces compression in all cases), or a numerical
+      integer value (which is equivalent to "on", but specifies the minimum
+      amount of data before the output is compressed). If the content-length is
+      not known and compression is set to "on" or more aggressive, the output
+      will also be compressed. If not specified, this attribute is set to
+      "off".</p>
+      <p><em>Note</em>: There is a tradeoff between using compression (saving
+      your bandwidth) and using the sendfile feature (saving your CPU cycles).
+      If the connector supports the sendfile feature, e.g. the NIO2 connector,
+      using sendfile will take precedence over compression. The symptoms will
+      be that static files greater that 48 Kb will be sent uncompressed.
+      You can turn off sendfile by setting <code>useSendfile</code> attribute
+      of the protocol, as documented below, or change the sendfile usage
+      threshold in the configuration of the
+      <a href="../default-servlet.html">DefaultServlet</a> in the default
+      <code>conf/web.xml</code> or in the <code>web.xml</code> of your web
+      application.
+      </p>
+    </attribute>
+    <attribute name="compressionMinSize" required="false">
+      <p>If <strong>compression</strong> is set to "on" then this attribute
+      may be used to specify the minimum amount of data before the output is
+      compressed. If not specified, this attribute is defaults to "2048".</p>
+    </attribute>
     <attribute name="initialWindowSize" required="false">
       <p>Controls the initial size of the flow control window for streams that
       Tomcat advertises to clients. If not specified, the default value of
@@ -139,6 +179,15 @@
       means no limit. If not specified, a default of 8192 is used.</p>
+    <attribute name="noCompressionUserAgents" required="false">
+      <p>The value is a regular expression (using <code>java.util.regex</code>)
+      matching the <code>user-agent</code> header of HTTP clients for which
+      compression should not be used,
+      because these clients, although they do advertise support for the
+      feature, have a broken implementation.
+      The default value is an empty String (regexp matching disabled).</p>
+    </attribute>
     <attribute name="readTimeout" required="false">
       <p>The time, in milliseconds, that Tomcat will wait for additional data
       when a partial HTTP/2 frame has been received. Negative values will be

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to