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 [1]

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 [2]

Version-Release number of selected component (if applicable):
BPM Suite 6.2.0

How reproducible:
Always

Steps to Reproduce:
1. Download file from dashbuilder - observe the HTTP response headers

Actual results:
Response contains header:
"Content-Coding: UTF-8" which does not conform to HTTP specification

Expected results:
The header should either contain valid tokens, or should be removed.

Additional info:
[1] https://en.wikipedia.org/wiki/HTTP_compression#Content-Encoding_tokens
[2] https://github.com/droolsjbpm/dashboard-builder/search?utf8=%E2%9C%93&q=Content-Encoding&type=Code