1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260
|
.. Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
.. include:: ../../common.defs
.. _admin-plugins-compress:
Compress Plugin
***************
This plugin adds compression and decompression options to both origin and cache
responses.
Purpose
=======
Not all clients can handle compressed content. Not all origin servers are
configured to respond with compressed content when a client says it can accept
it. And it's not always necessary to make two separate requests to an origin,
and track two separate cache objects, for the same content - once for a
compressed version and another time for an uncompressed version.
This plugin tidies up these problems by transparently compressing or deflating
origin responses, as necessary, so that both variants of a response are stored
as :term:`alternates <alternate>` and the appropriate version is used for client responses,
depending on the client's indication (via an ``Accept`` request header) of what
it can support.
Additionally, this plugin adds configurability for what types of origin
responses will receive this treatment, which will be proxied and cached with
default behavior, and which may be explicitly disallowed to cache both
compressed and deflated versions (because, for example, the cost of compression
is known ahead of time to outweigh the space and bandwidth savings and you wish
to avoid |TS| even testing for the possibility).
Installation
============
This plugin is considered stable and is included with |TS| by default. There
are no special steps necessary for its installation.
Configuration
=============
This plugin can be used as either global plugin or remap plugin.
It can be enabled globally for |TS| by adding the following to your
:file:`plugin.config`::
compress.so
With no further options, this will enable the following default behavior:
* Enable caching of both compressed and uncompressed versions of origin
responses as :term:`alternates <alternate>`.
* Compress objects with `text/*` content types for every origin.
* Don't hide `Accept` encoding headers from origin servers (for an offloading
reverse proxy).
* No URLs are disallowed from compression.
* Disable flush (flush compressed content to client).
* Only objects greater than 1Kb will be compressed
Alternatively, a configuration may be specified (shown here using the sample
configuration provided with the plugin's source)::
compress.so <path-to-plugin>/sample.compress.config
This can be used as remap plugin by pointing to config file in remap rule
:file:`remap.config`::
@plugin=compress.so @pparam=sample.compress.config
The following sections detail the options you may specify in the plugin's
configuration file. Options may be used globally, or may be specified on a
per-site basis by preceding them with a `[<site>]` line, where `<site>` is the
client-facing domain for which the options should apply.
Per site configuration for remap plugin should be ignored.
cache
-----
When set to ``true``, causes |TS| to cache both the compressed and uncompressed
versions of the content as :term:`alternates <alternate>`. When set to
``false``, |TS| will cache only the compressed or decompressed variant returned
by the origin. Enabled by default.
range-request
-------------
When set to ``true``, causes |TS| to compress responses to Range Requests.
Disabled by default. Setting this to true while setting cache to false leads to delivering corrupted content.
compressible-content-type
-------------------------
Provides a wildcard to match against content types, determining which are to be
considered compressible. This defaults to ``text/*``. Takes one Content-Type
per line.
compressible-status-code
------------------------
A comma separated list of response status codes for which to enable
compression. Defaults to 200, 206, 304.
minimum-content-length
----------------------
Minimum Content-Length value sent by the origin server to consider the response
compressible. Due to the overhead and latency of compression and decompression,
it only makes sense to compress files above a certain size threshold.
Compressing files below 150 bytes can actually make them larger. This setting
only applies if the response explicitly sends Content-Length. Regardless of
this setting, responses with ``Content-Length: 0`` are considered not
compressible.
allow
--------
Provides a wildcard pattern which will be applied to request URLs. Any which
match the pattern will be considered compressible, and only deflated versions
of the objects will be cached and returned to clients. This may be useful for
objects which already have their own compression built-in, to avoid the expense
of multiple rounds of compression for trivial gains. If the regex is preceded by
``!`` (for example ``allow !*/nothere/*``), it disables the plugin from those machine URLs.
enabled
-------
When set to ``true`` (the default) permits objects to be compressed, and when ``false``
effectively disables the plugin in the current context.
flush
-----
Enables (``true``) or disables (``false``) flushing of compressed objects to
clients. This calls the compression algorithm's mechanism (Z_SYNC_FLUSH and for gzip
and BROTLI_OPERATION_FLUSH for brotli) to send compressed data early.
remove-accept-encoding
----------------------
When set to ``true`` this option causes the plugin to strip the request's
``Accept-Encoding`` header when contacting the origin server. Setting this option to ``false``
will leave the header intact if the client provided it.
* To ease the load on the origins.
* For when the proxy parses responses, and the resulting compression and
decompression is wasteful.
supported-algorithms
----------------------
Provides the compression algorithms that are supported, a comma separate list
of values. This will allow |TS| to selectively support ``gzip``, ``deflate``,
and brotli (``br``) compression. The default is ``gzip``. Multiple algorithms can
be selected using ',' delimiter, for instance, ``supported-algorithms
deflate,gzip,br``. Note that this list must **not** contain any white-spaces!
Note that if :ts:cv:`proxy.config.http.normalize_ae` is ``1``, only gzip will
be considered, and if it is ``2``, only br or gzip will be considered.
Examples
========
To establish global defaults for all site requests passing through |TS|, while
overriding just a handful for requests to content at ``www.example.com``, you
might create a configuration with the following options::
# Set some global options first
cache true
remove-accept-encoding false
compressible-content-type text/*
compressible-content-type application/json
compressible-status-code 200, 206
minimum-content-length 860
flush false
# Now set a configuration for www.example.com
[www.example.com]
cache false
remove-accept-encoding true
allow !/notthis/*.js
allow /this/*.js
flush true
# Allows brotli encoded response from origin but is not capable of brotli compression
[brotli.allowed.com]
enabled true
compressible-content-type text/*
compressible-content-type application/json
flush true
supported-algorithms gzip,deflate
# Supports brotli compression
[brotli.compress.com]
enabled true
compressible-content-type text/*
compressible-content-type application/json
flush true
supported-algorithms br,gzip
# This origin does it all
[bar.example.com]
enabled false
# A reasonable list of content-types that are compressible
compressible-content-type text/*
compressible-content-type *font*
compressible-content-type *javascript
compressible-content-type *json
compressible-content-type *ml;*
compressible-content-type *mpegURL
compressible-content-type *mpegurl
compressible-content-type *otf
compressible-content-type *ttf
compressible-content-type *type
compressible-content-type *xml
compressible-content-type application/eot
compressible-content-type application/pkix-crl
compressible-content-type application/x-httpd-cgi
compressible-content-type application/x-perl
compressible-content-type image/vnd.microsoft.icon
compressible-content-type image/x-icon
Assuming the above options are in a file at ``/etc/trafficserver/compress.config``
the plugin would be enabled for |TS| in :file:`plugin.config` as::
compress.so /etc/trafficserver/compress.config
Alternatively, the compress plugin can be used as a remap plugin: ::
map http://www.example.com http://origin.example.com \
@plugin=compress.so @pparam=compress.config
$ cat /etc/trafficserver/compress.config
enabled true
cache true
compressible-content-type *xml
supported-algorithms
|