[HTTPCORE-328] EntityUtils#toString ignores default charset parameter if there is no ContentType in the http response

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.2.3
• Fix Version/s: 4.2.4, 4.3-beta1
• Component/s: HttpCore
• Labels: bug, charset, httpcore
• Environment: Eclipse 3.7 SR2; Oracle Java EE 1.6.0; Windows XP SP3
• Assignee: Unassigned
• Reporter: kuyurmoe
• Created: 16/Jan/13 10:40
• Updated: 05/Oct/13 20:09
• Resolved: 18/Jan/13 11:13

Description

There is a http response with 500 status and error message encoded in UTF-8 in ContentBody, but without ContentType header.
When using EntityUtils.toString to get message like:
EntityUtils.toString(response.getEntity(), "UTF-8")
the defaultCharset will never work.

The real charset becomes ISO_8859_1 because ContentType.getOrDefault(entity) will return a ContentType holding a never null charset(ISO_8859_1). It can not be overrided by defaultCharset anymore.

Issue Links

• is duplicated by: HTTPCORE-329 EntityUtils.toString uses wrong charset if no content-type is provided by server