Skip to main content
Version: v6

Compression

Configure compression or decompression of responses

Overview

Haltdos provides you the ability to compress or decompress the responses which often significantly reduce the size of transmitted data and increase performance. The compression level is defined based on which responses are compressed to an extent. It also allows configuring other settings for compression.

Caching

How to Use :

  1. Go to WAF > Listeners > Performance > Compression
  2. Click on **Add Compression Configuration **
  3. Click Save Changes
ParametersAccepted ValuesDefault
Enable CompressionEnabled/DisabledDisabled
Compression LevelInteger (1-9)1
Min Length CompressionLength in bytes1000
Disable CompressionRegexBlank
Minimum HTTP versionDrop-downHTTP 1.1
URI FilterURI RegexBlank
Proxy Response Filterexpired/no-cache/no-store/private/no_last_modified/no_etag/any/authexpired, no-cache, no-store, private, no_last_modified, no_etag, any, auth
Mime Type FilterAny mime typetext/xml , text/plain
De-CompressionEnabled/DisabledDisabled

Compression

Description

1.Enable Compression

To enable compression, enable the toggle button. It compresses the responses to an extent.

2.Compression Level

The level of compression to be achieved. The greater the number more the compression. The range is 1 - 9.

3.Min Length Compression

This field specifies the minimum length of the response to be compressed.

4.Disable Compression

Specify one or more regular expressions (Regex) that will be evaluated on HTTP requests and disable compression for matching requests.

5.Minimum HTTP Version

Specify the minimum HTTP version from which compression will be applied. The response above the specified version is compressed.

6.URI Filter

This field allows to perform compression on the specific URI using one or more regex. If the field is empty then no filter perform.

7.Proxy Response Filter

This field allows to perform compression on the specific type of HTTP requests.

8.Mime Type Filter

By default, WAF compresses responses only with MIME-type text/HTML. To compress responses with other MIME types then include them in this field.

9.De-Compression

Some clients do not support responses with the GZIP encoding method. At the same time, it might be desirable to store compressed data, or compress responses on the fly and store them in the cache. To successfully serve both clients that do and do not accept compressed data, WAF can decompress data on the fly when sending it to the latter type of client.