Hi all,
I just upgraded customers Geoserver from 2.3.1 to 2.3.5 and it seems that something has changed in encoding handling. Some of the configured layers have ä’s & ö’s In their title and this has previously worked ok. After upgrading, if layer configuration is saved encoding in title is broken, so end result is complete gibberish like so:
Pyörätiet → Pyörätiet
Pylväät → Pylväät
So it looks like it is double encoded. I could fix this by using recode UTF-8…latin1 featuretype.xml, but saving layer configuration will break it again. I remember similar behavior with 2.0 series of Geoserver, but this has worked fine since 2.1+ until now. Does anyone else have this issue or is it possible that some exotic configuration (which I don’t think we have, but you never know) could affect this?
Br,
Tuomas Koivusalo