public void setEnableAcceptEncodingBrotli(Boolean enableAcceptEncodingBrotli) {
        this.enableAcceptEncodingBrotli = enableAcceptEncodingBrotli;
    }
<p>
A flag that can affect whether the <code>Accept-Encoding</code> HTTP header is included in the cache key and
included in requests that CloudFront sends to the origin.
</p>
<p>
This field is related to the <code>EnableAcceptEncodingGzip</code> field. If one or both of these fields is
<code>true</code> <i>and</i> the viewer request includes the <code>Accept-Encoding</code> header, then CloudFront
does the following:
</p>
<ul>
<li>
<p>
Normalizes the value of the viewer's <code>Accept-Encoding</code> header
</p>
</li>
<li>
<p>
Includes the normalized header in the cache key
</p>
</li>
<li>
<p>
Includes the normalized header in the request to the origin, if a request is necessary
</p>
</li>
</ul>
<p>
For more information, see <a href=
"https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/controlling-the-cache-key.html#cache-policy-compressed-objects"
>Compression support</a> in the <i>Amazon CloudFront Developer Guide</i>.
</p>
<p>
If you set this value to <code>true</code>, and this cache behavior also has an origin request policy attached,
do not include the <code>Accept-Encoding</code> header in the origin request policy. CloudFront always includes
the <code>Accept-Encoding</code> header in origin requests when the value of this field is <code>true</code>, so
including this header in an origin request policy has no effect.
</p>
<p>
If both of these fields are <code>false</code>, then CloudFront treats the <code>Accept-Encoding</code> header
the same as any other HTTP header in the viewer request. By default, it's not included in the cache key and it's
not included in origin requests. In this case, you can manually add <code>Accept-Encoding</code> to the headers
whitelist like any other HTTP header.
</p>

@param enableAcceptEncodingBrotli
       A flag that can affect whether the <code>Accept-Encoding</code> HTTP header is included in the cache key
       and included in requests that CloudFront sends to the origin.</p>
       <p>
       This field is related to the <code>EnableAcceptEncodingGzip</code> field. If one or both of these fields
       is <code>true</code> <i>and</i> the viewer request includes the <code>Accept-Encoding</code> header, then
       CloudFront does the following:
       </p>
       <ul>
       <li>
       <p>
       Normalizes the value of the viewer's <code>Accept-Encoding</code> header
       </p>
       </li>
       <li>
       <p>
       Includes the normalized header in the cache key
       </p>
       </li>
       <li>
       <p>
       Includes the normalized header in the request to the origin, if a request is necessary
       </p>
       </li>
       </ul>
       <p>
       For more information, see <a href=
       "https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/controlling-the-cache-key.html#cache-policy-compressed-objects"
       >Compression support</a> in the <i>Amazon CloudFront Developer Guide</i>.
       </p>
       <p>
       If you set this value to <code>true</code>, and this cache behavior also has an origin request policy
       attached, do not include the <code>Accept-Encoding</code> header in the origin request policy. CloudFront
       always includes the <code>Accept-Encoding</code> header in origin requests when the value of this field is
       <code>true</code>, so including this header in an origin request policy has no effect.
       </p>
       <p>
       If both of these fields are <code>false</code>, then CloudFront treats the <code>Accept-Encoding</code>
       header the same as any other HTTP header in the viewer request. By default, it's not included in the cache
       key and it's not included in origin requests. In this case, you can manually add
       <code>Accept-Encoding</code> to the headers whitelist like any other HTTP header.
aws-java-sdk-cloudfront/src/main/java/com/amazonaws/services/cloudfront/model/ParametersInCacheKeyAndForwardedToOrigin.java