Solutions

The ProxySG indicates a content encoding error when downloading a file.

Solutions ID:    KB4994
Version:    2.0
Status:    Published
Published date:    03/13/2012
Updated:    11/05/2013
 

Problem Description

A website or page is returning a content encoding error.

After setting a block policy on executable files, the ProxySG blocks files with a multi-encoded file extension (such as xxxx.tar.gz.enc), and displays an exception page when attempting to perform a file download.


Policy Example:


;Installed Policy -- compiled at:
;    Default proxy policy is ALLOW

;Policy Rules
<Proxy>
    Deny http.response.apparent_data_type=executable

 

ProxySG exception page example:


 

Resolution

 This issue is typically caused by the OCS presenting a content encoding header of one type, but then encoding the data differently.

Workaround 1: Remove the Accept-Encoding header from outbound responses. The OCS admin should also be made aware that they are delivering incorrect data.

Here are three ways to approach the issue.

#1. Modify the Accept-Encoding header via policy.

  1. Add a new rule at the top of the web access layer.
  • Destination: Create a URL object that does a simple match on "domain.com," where "domain.com" is the site that you are having issues with.
  • Action field: Set - New - Action field > suppress headers> select request radio button> accept-encoding - ok.
  1. Install policy.

This will have the affect of removing/suppressing the client/browser's request header Accept-Encoding.

#2. Bypass cache for this site.

1. Add a new rule at the top of the web access layer.

  • Destination: Create a URL object that does a simple match on "domain.com," where "domain.com" is the site that you are having issues with.
  • Action field: Set - Bypass Cache, from the list - ok.

2. Install policy

This will have the affect of removing/supressing the client/browser's request header Accept-Encoding.

#3 Use a bypass cache CPL :

<Cache>
    url.domain="domain.com" cache(no)

 

Workaround 2: Disable the http.response.apparent_data_type policy rule.

 

Workaround 3: Contact the site administrator and request that she/he stops sending the Content-Encoding header.



Rate this Page

Please take a moment to complete this form to help us better serve you.

Did this document help answer your question?
 
 
If you are finished providing feedback, please click the RATE CONTENT button. Otherwise, please add more detail in the following text box and then click RATE CONTENT.
 
 

Your response will be used to improve our document content.

Ask a Question