Affects Version/s: 5.3.2, 5.3.3, 5.3.4, 5.3.5, 5.3.6
Fix Version/s: None
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.
|Affects Version/s||5.3.3 [ 12320045 ]|
|Affects Version/s||5.3.6 [ 12322961 ]|
|Affects Version/s||5.3.5 [ 12322440 ]|
|Affects Version/s||5.3.4 [ 12320774 ]|
|Status||Open [ 1 ]||Closed [ 6 ]|
|Assignee||Howard M. Lewis Ship [ hlship ]|
|Resolution||Fixed [ 1 ]|