|
Issue Type:
|
 Bug
|
|
Affects Versions:
|
2.1.4
|
|
Assignee:
|
Andrea Aime
|
|
Attachments:
|
json-utf8.diff
|
|
Components:
|
WFS
|
|
Created:
|
22/Oct/12 8:12 AM
|
|
Description:
|
JSON RFC [1] says in Section 3 Encoding: “JSON text SHALL be encoded in
Unicode. The default encoding is UTF-8.”
But geoserver’s default encoding for json output is taken from global
encoding setting, which can be different to UTF-8 and therefor be not
unicode.
Today, many JSON parsers expect UTF-8 but get for example iso-8859-1 and
throw exceptions when handling special characters (german language).
But setting global encoding to UTF-8 could break compatibility to
existing WFS client apps and is therefor not so good.
[1] http://www.ietf.org/rfc/rfc4627.txt
|
|
Environment:
|
linux java6
|
|
Fix Versions:
|
2.1.x
|
|
Project:
|
GeoServer
|
|
Priority:
|
 Major
|
|
Reporter:
|
Rudi Hochmeister
|
|
Original Estimate:
|
1 hour
|
|
Remaining Estimate:
|
1 hour
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your [JIRA administrators](https://jira.codehaus.org/secure/ContactAdministrators!default.jspa).
For more information on JIRA, see: [http://www.atlassian.com/software/jira](http://www.atlassian.com/software/jira)
