Show search and navigation.

 

Troubleshooting Edge Server Compression

Purpose

The purpose of this procedure is to troubleshoot issues with edge server compression.

Related Topic

Media Type

Edge server compression will only be performed for the media typeIdentifies/classifies the data contained in a file.s (aka content type) defined on the Compression page.

The Content-Type response header indicates the media type associated with an asset.

Checklist:

Check whether the request's media type is set within the File Types option on the Compression page.

Cached Content

Edge server compression may only be applied to freshIdentifies cached content that can be served directly by an edge server without requiring revalidation with an origin server. It also indicates that the cached content's TTL has not expired. content.

Content may only be cached as it is requested at the POP closest to the requester.

The value returned for the Server response header will use the following syntax for cached content:

EOS (POP/IDIndicates a four digit alphanumeric system ID. This field is used solely for internal purposes.)

Learn more.

Checklist:

Verify that the requested content has been previously cached in the region where it is being requested.

File Size

Edge server compression may only be applied to files:

  • Larger than 128 bytes.
  • Smaller than 1 MB.

Checklist:

Verify that the content in question complies with the above file size requirements.

Accept-Encoding Request Header

Compression may only be applied to requests that include an Accept-Encoding header set to one of the following formats:

  • gzip
  • deflate
  • bzip2

Checklist:

Verify that the request includes the Accept-Encoding header.

Verify that the Accept-Encoding header is set to a supported format.