Show search and navigation.

 

Troubleshooting Origin Server 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.

Purpose

The purpose of this procedure is to troubleshoot issues compressing content on a customer origin server.

Related Topic

Accept-Encoding Request Header

Compression may only be applied to requests that include an Accept-Encoding header. This request header must be set to a format (e.g., gzip, deflate, or bzip2) supported by your web server.

Checklist:

Verify that the request includes the Accept-Encoding header.

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

IIS Web Server Only

An IIS server will not compress requests that contain a Via header. This issue can be resolved by either:

  • Disabling this behavior on the IIS server.

  • Setting up Rules Engine to strip the Via header from the request proxied to the origin server. This configuration may be achieved by creating the following rule:

    • Match: It should match requests to any customer origin server that points to an IIS server.
    • Feature: It should contain the Proxy Special Headers feature. Make sure that the value assigned to this feature does not contain "via."
      Sample value:
      x-forwarded-proto x-host x-midgress

Additional Information

The Via request header indicates that a user's request is being proxied through our network to the origin server (e.g., IIS server). By default, an IIS server will not serve compressed content for proxied requests, since it assumes that a proxy server cannot handle compressed content.

Checklist:

Verify that requests do not include the Via request header.