Hello Devs, Before starting I'd like to acknowledge I did not read the the Getting Involved section in the Community page on Tapestry's site and therefore did not discuss with you guys a problem I was having before posting a Jira issue.
That out of the way, and since it seems a 5.3.4 release is forming, I'd like to get your opinion on the issue: 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. Thanks! Nelson Rodrigues.