[CAMEL-20037] camel-http builds StringEntity with wrong contentEncoding

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0.1, 4.1.0
• Fix Version/s: 4.0.3, 4.2.0
• Component/s: camel-http
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: Simo Kivimäki
• Created: 24/Oct/23 10:53
• Updated: 23/Nov/23 11:10
• Resolved: 25/Oct/23 09:05

Description

HttpProducer.java line 781:

answer = new StringEntity(content, contentType, charset, false);

Here the third parameter should be contentEncoding (e.g. null). Not charset.

This will produce HTTP request having for example header:

Content-Encoding: utf-8

UTF-8 is not allowed Content-Encoding. See https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Encoding.

Some http servers returns HTTP 415 Unsupported Media Type because of that.

Issue Links

• is duplicated by: CAMEL-20099 Camel-http is creating invalid Content-Encoding header based on charset from Content-Type header
• links to: GitHub Pull Request #11828