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

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TAP5-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14083078#comment-14083078 ] 

ASF subversion and git services commented on TAP5-1900:
-------------------------------------------------------

Commit d29d6dc59df407f2f9f1b0adbdcd25bb4a3dc775 in tapestry-5's branch refs/heads/master from [~hlship]
[ https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;h=d29d6dc ]

TAP5-1900: Provide better control over Response character set, using value specified in Request if possible


> Tapestry always uses application charset for request encoding, should first check content-type header
> -----------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1900
>                 URL: https://issues.apache.org/jira/browse/TAP5-1900
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3.2, 5.3.3, 5.3.4, 5.3.5, 5.3.6
>            Reporter: Nelson Rodrigues
>            Assignee: Howard M. Lewis Ship
>         Attachments: tap5-1900.patch
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2#6252)