[FLINK-5109] Invalid Content-Encoding Header in REST API responses

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.2.0
• Fix Version/s: 1.2.0
• Component/s: Runtime / Web Frontend
• Labels: http-headers rest_api
• Flags: Patch
• Assignee: Unassigned
• Reporter: Móger Tibor László
• Created: 21/Nov/16 12:18
• Updated: 28/Feb/19 13:34
• Resolved: 03/Dec/16 17:31

Description

On REST API calls the Flink runtime responds with the header Content-Encoding, containing the value "utf-8". According to the HTTP/1.1 standard this header is invalid. ( https://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.5 )
Possible acceptable values are: gzip, compress, deflate. Or it should be omitted.
The invalid header may cause malfunction in projects building against Flink.

The invalid header may be present in earlier versions aswell.

Proposed solution: Remove lines from the project, where CONTENT_ENCODING header is set to "utf-8". (I could do this in a PR.)

Possible solution but may need further knowledge and skills than mine: Introduce content-encoding. Doing so may need some configuration beacuse then Flink would have to encode the responses properly (even paying attention to the request's Accept-Encoding headers).

Issue Links

• links to: GitHub Pull Request #2892
• links to: GitHub Pull Request #2898
• links to: GitHub Pull Request #3432