Show search and navigation.

 

Compression

Applies To:
HTTP LargeThis platform has been optimized to cache and deliver static content (e.g., HTML, CSS, JavaScript, ISO, multimedia, and software downloads, etc.) over HTTP or HTTPS.
HTTP SmallLegacy. If you are currently serving traffic over this platform, then you may continue to do so. However, we recommend that you serve your traffic over our more robust HTTP Large platform.
ADNThe Application Delivery Network platform has been optimized to deliver dynamic content (e.g., login credentials, account information, etc.) over HTTP or HTTPS. Typically, user-specific and database-driven content are served over this platform.

Reduce the amount of bandwidth required to deliver an asset through compression. An asset may be compressed by an external web server or by the CDN. A brief description for each compression method is provided below.

Type Description

External Web Server

An asset may be compressed on an external web server.

This allows:

  • A customer origin server to serve a compressed version of the requested content via the CDN. This improves performance by reducing the amount of data transferred between the customer origin server and the requesterRefers to the user that requested content..
  • The compressed version of the requested content to be cached on the edge server that fulfilled the request.

Edge Server

Content may be compressed by the CDN as it is requested. After which, the compressed version of the requested content may be cached on an edge server.