[
https://issues.apache.org/jira/browse/AXIS2C-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski resolved AXIS2C-1505.
-------------------------------------
Resolution: Not A Problem
This behavior is intentional and follows HTTP/1.1 (RFC 2616):
"When no explicit charset parameter is provided by the sender, media
subtypes of the 'text' type are defined to have a default charset
value of 'ISO-8859-1' when received via HTTP."
Why GBK "worked":
The user likely had browser/client settings defaulting to GBK on their
CentOS 5.4 system. When they explicitly set UTF-8 without specifying
charset in Content-Type, the server assumed ISO-8859-1, causing
garbled text.
Correct Solution (Client-side):
Always specify charset in Content-Type header:
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
> encoding fault with axis2c
> --------------------------
>
> Key: AXIS2C-1505
> URL: https://issues.apache.org/jira/browse/AXIS2C-1505
> Project: Axis2-C
> Issue Type: Bug
> Components: REST
> Affects Versions: 1.6.0
> Environment: centos 5.4
> Reporter: shawndeng
> Priority: Major
> Original Estimate: 100h
> Remaining Estimate: 100h
>
> I setup axis2c and did not set any special parameter. Just built a simple
> RESTfull http post service. When I test the service, if I use "GBK" as the
> encoding charset, axis server can read chinese character correctly, but if I
> use "utf-8" or any other encoding, server side can not read Chinese character.
> I think the default encoding is "utf-8" and I am quite sure that I didn't set
> any parameter related to character encoding. So why I have to set the
> encoding to "GBK" in the client side?
> My project demand us to use "utf-8" as the encoding charset. Can you help me
> on this issue or give me some suggestions? I want to know how to set up
> encoding charset in axis2c.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
