Hi All,
I have sent this post several times to the geoserver-user list, but I got no response.
Sorry if I am off topic, but this seems to be quite a general issue and it may be a bug.
here is my post ...
I am migrating data from Geoserver 1.7.2 to 2.3.0. When I connect a
specific WMS layer from Geoserver 1.7.2 to Geonetwork, the map viewer
displays getFeatureInfo response properly. When I connect the same
layer
from Geoserver 2.3.0 Geonetwork map viewer fails to show UTF-8
characters. The reason is probably the Content-Type parameter in the HTTP
response header.
Geoserver 1.7.2 sends:
Content-Type: text/plain;charset=UTF-8
Geoserver 2.3.0 sends:
Content-Type: text/plain
Having no charset declared the Geonetwork client misinterprets the
encoding and messes up the output.
Is there any way to make Geoserver 2.3.0 send a complete HTTP header,
so the client knows that it recieves a UTM-8 text?
Best regards,
Laszlo S.
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users