tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nelson Rodrigues (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (TAP5-1900) Tapestry always uses application charset for request encoding, should first check content-type header
Date Thu, 12 Apr 2012 10:37:17 GMT
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
            Reporter: Nelson Rodrigues


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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message