By default, encodings are normalized to either Identity or Gzip. Any other encodings are automatically dropped from the request. However, you may override this by creating an accept-encoding definition that is attached to a property-based setting.
Creating an accept-encoding definition allows you to specify extensions and compression types that should be accepted if included in a client’s request. Please note that the CDN will not transform or compress files. The file and compression types must be supported by the origin. Furthermore, normalization never causes the Lumen CDN to serve an encoding that was not requested or that the client has specified as unacceptable.