tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (TAP5-1900) Tapestry always uses application charset for request encoding, should first check content-type header
Date Fri, 01 Aug 2014 22:29:39 GMT

     [ https://issues.apache.org/jira/browse/TAP5-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Howard M. Lewis Ship closed TAP5-1900.
--------------------------------------

    Resolution: Fixed
      Assignee: Howard M. Lewis Ship

> 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)

Mime
View raw message