[TAP5-1900] Tapestry always uses application charset for request encoding, should first check content-type header

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.3.2, 5.3.3, 5.3.4, 5.3.5, 5.3.6
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Nelson Rodrigues
• Created: 12/Apr/12 10:36
• Updated: 02/Aug/14 04:21
• Resolved: 01/Aug/14 22:29

Description

I'm using Tapestry as a sort of REST server, using pages to act as REST gateways to business services.

To access those pages I'm using Spring's RestTemplate which as a default uses ISO-8859-1 as the request encoding and properly seting the request's content-type header.

Tapestry currently forces the request encoding to be the same as the application charset (see org.apache.tapestry5.internal.services.RequestImpl.setupEncoding), I believe it should first check the content-type header and use that value instead, only using application charset as a fallback.