|
|
|
Issue Type:
|
 Bug
|
|
Affects Versions:
|
2.4.0, 2.3.5
|
|
Assignee:
|
Andrea Aime
|
|
Components:
|
UI
|
|
Created:
|
11/Oct/13 10:56 AM
|
|
Description:
|
Starting from version 2.3.5, it looks like there’s an issue with non-ASCII characters in GeoServer forms.
I’ve encountered this behavior on several pages: “Edit layer”, “Edit Raster Data Source”, “Style Editor”, etc.
Basically, non-ASCII characters in the input get scrambled: for instance, “é” becomes “é” once processed by GeoServer.
However, it kind of depends on the browser: that is, how they POST the HTML forms or, more precisely, the “Content-Type” header in the request.
E.g.:
POST /geoserver235/web/?wicket:… HTTP/1.1
…
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
Taking for example the “Edit Layer” page:
- Using Google Chrome, which only sends “Content-Type: application/x-www-form-urlencoded”: the Name, Title or Keywords (and other) fields fail to properly save non-ASCII data.
- Same problem using Firefox, except for the “Keywords” field, for which Firefox happens to send “Content-Type: application/x-www-form-urlencoded; charset=UTF-8”.
I’ve compared with GeoServer 2.3.4: everything works fine at that version, I don’t get the bug as in 2.3.5 and 2.4.0.
Tested on Linux, with Tomcat 6 and 7.
|
|
Project:
|
GeoServer
|
|
Priority:
|
 Major
|
|
Reporter:
|
John Doe
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: [http://www.atlassian.com/software/jira](http://www.atlassian.com/software/jira)