Red Hat Bugzilla – Bug 1252257
Dashbuilder sets nonsensical "Content-Encoding" header in Ajax responses
Last modified: 2016-01-08 16:55:32 EST
Description of problem:
After upgrading version of Apache HTTP client we use in our tests to verify validity of export files I started getting the following exception:
"org.apache.http.HttpException: Unsupported Content-Encoding: UTF-8"
This forces us to do some workarounds in the tests to ignore this header.
I browsed HTTP specification and found out, that the meaning of the "Content-Encoding" header is to specify for example if compression is applied (value like "Content-Encoding: gzip" and NOT character encoding. See for list of valid tokents for Content-Encoding 
Please find all places where this is set and either remove the header-setting code or fix it to some valid value. Preliminary search reveals several occurrences where Content-Encoding is set to character encoding 
Version-Release number of selected component (if applicable):
BPM Suite 6.2.0
Steps to Reproduce:
1. Download file from dashbuilder - observe the HTTP response headers
Response contains header:
"Content-Coding: UTF-8" which does not conform to HTTP specification
The header should either contain valid tokens, or should be removed.