You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Parth Brahmbhatt (JIRA)" <ji...@apache.org> on 2014/11/14 00:53:35 UTC
[jira] [Updated] (STORM-555) Storm Json response encoding should be
UTF-8
[ https://issues.apache.org/jira/browse/STORM-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Parth Brahmbhatt updated STORM-555:
-----------------------------------
Description:
Currently the storm Rest API responses has charset=iso-8859-1 set by ring/jetty by default. However on html pages we have meta tag set to UTF-*. The response charset should be set to UTF-8 to support GB18030.
To reproduce: submit a storm topology with non ascii characters like '䶴ㄩ鼾丄狜〇'. In the UI the topology name will be displayed incorrectly with '??????' . This is applicable to bolt and spout names or anything in reponse that might have non ascii characters.
In addition because of incorrect charset no topology actions can be performed on topoogies with nonascii character.
was:
Currently the storm Rest API responses has charset=iso-8859-1 set by ring/jetty by default. However on html pages we have meta tag set to UTF-*. The response charset should be set to UTF-8 to support GB18030.
To reproduce: submit a storm topology with non ascii characters like '䶴ㄩ鼾丄狜〇'. In the UI the topology name will be displayed incorrectly with '??????' . This is applicable to bolt and spout names or anything in reponse that might have non ascii characters.
> Storm Json response encoding should be UTF-8
> --------------------------------------------
>
> Key: STORM-555
> URL: https://issues.apache.org/jira/browse/STORM-555
> Project: Apache Storm
> Issue Type: Bug
> Reporter: Parth Brahmbhatt
> Assignee: Parth Brahmbhatt
> Priority: Minor
>
> Currently the storm Rest API responses has charset=iso-8859-1 set by ring/jetty by default. However on html pages we have meta tag set to UTF-*. The response charset should be set to UTF-8 to support GB18030.
> To reproduce: submit a storm topology with non ascii characters like '䶴ㄩ鼾丄狜〇'. In the UI the topology name will be displayed incorrectly with '??????' . This is applicable to bolt and spout names or anything in reponse that might have non ascii characters.
> In addition because of incorrect charset no topology actions can be performed on topoogies with nonascii character.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)