[Geoserver-users] Possible regression in encoding handling in Geoserver 2.3.5

GeoServer GeoServer User
1

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

2

There was an issue and it should be fixed since 2.3.1 (http://jira.codehaus.org/browse/GEOS-5641) Wondering what has been changed since…

Could you please check the properties file encodings. I may be that some files are UTF-8 I guess.

Have you tried with 2.4-RC1 - same probem here?

  • Frank
···

2013/9/3 Koivusalo, Tuomas <tuomas.koivusalo@anonymised.com>

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

Learn the latest–Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk

Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

3

Just an additional question : Which language have you configured in you browser? Makes it easier to find the problematic file :wink:

Thanks

  • Frank
···

2013/9/3 Frank Gasdorf <fgdrf@anonymised.com>

There was an issue and it should be fixed since 2.3.1 (http://jira.codehaus.org/browse/GEOS-5641) Wondering what has been changed since…

Could you please check the properties file encodings. I may be that some files are UTF-8 I guess.

Have you tried with 2.4-RC1 - same probem here?

  • Frank

2013/9/3 Koivusalo, Tuomas <tuomas.koivusalo@anonymised.com>

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

Learn the latest–Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk

Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

4

Hi,

It seems that most of the files are in us-ascii encoding, layer featuretype.xml's are for some part in utf-8 (by quickly glancing through list I'd say that layers containing Scandinavian letters are in UTF-8, otherwiser us-ascii). None of the properties files seem to be in UTF-8.

My browser is configured to use English.

I'm downloading 2.4-RC1 right now, I'll check if I can replicate issue there.

Br,

Tuomas Koivusalo

-----Original Message-----
From: frank.gasdorf@anonymised.com [mailto:frank.gasdorf@anonymised.com] On Behalf Of Frank Gasdorf
Sent: 3. syyskuuta 2013 15:39
To: Koivusalo, Tuomas; geoserver
Subject: Re: [Geoserver-users] Possible regression in encoding handling in Geoserver 2.3.5

Just an additional question : Which language have you configured in you browser? Makes it easier to find the problematic file :wink:

Thanks
- Frank

2013/9/3 Frank Gasdorf <fgdrf@anonymised.com>

  There was an issue and it should be fixed since 2.3.1 (http://jira.codehaus.org/browse/GEOS-5641) Wondering what has been changed since...

  Could you please check the properties file encodings. I may be that some files are UTF-8 I guess.

  Have you tried with 2.4-RC1 - same probem here?

  - Frank

  2013/9/3 Koivusalo, Tuomas <tuomas.koivusalo@anonymised.com>

    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
    
    ------------------------------------------------------------------------------
    Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
    Discover the easy way to master current and previous Microsoft technologies
    and advance your career. Get an incredible 1,500+ hours of step-by-step
    tutorial videos with LearnDevNow. Subscribe today and save!
    http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
    _______________________________________________
    Geoserver-users mailing list
    Geoserver-users@lists.sourceforge.net
    https://lists.sourceforge.net/lists/listinfo/geoserver-users
    

5

Hi,

It would seem like 2.4-RC1 suffers from same issue. It looks like encoding is changed to UTF-8 if I try to enter ä or ö to title, causing the problem. I checked layer xmls with file -bi before and after testing it.

-Tuomas

-----Original Message-----
From: Koivusalo, Tuomas [mailto:tuomas.koivusalo@anonymised.com]
Sent: 3. syyskuuta 2013 15:46
To: fgdrf@anonymised.com; geoserver
Subject: Re: [Geoserver-users] Possible regression in encoding handling in Geoserver 2.3.5

Hi,

It seems that most of the files are in us-ascii encoding, layer featuretype.xml's are for some part in utf-8 (by quickly glancing through list I'd say that layers containing Scandinavian letters are in UTF-8, otherwiser us-ascii). None of the properties files seem to be in UTF-8.

My browser is configured to use English.

I'm downloading 2.4-RC1 right now, I'll check if I can replicate issue there.

Br,

Tuomas Koivusalo

-----Original Message-----
From: frank.gasdorf@anonymised.com [mailto:frank.gasdorf@anonymised.com] On Behalf Of Frank Gasdorf
Sent: 3. syyskuuta 2013 15:39
To: Koivusalo, Tuomas; geoserver
Subject: Re: [Geoserver-users] Possible regression in encoding handling in Geoserver 2.3.5

Just an additional question : Which language have you configured in you browser? Makes it easier to find the problematic file :wink:

Thanks
- Frank

2013/9/3 Frank Gasdorf <fgdrf@anonymised.com>

  There was an issue and it should be fixed since 2.3.1 (http://jira.codehaus.org/browse/GEOS-5641) Wondering what has been changed since...

  Could you please check the properties file encodings. I may be that some files are UTF-8 I guess.

  Have you tried with 2.4-RC1 - same probem here?

  - Frank

  2013/9/3 Koivusalo, Tuomas <tuomas.koivusalo@anonymised.com>

    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
    
    ------------------------------------------------------------------------------
    Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
    Discover the easy way to master current and previous Microsoft technologies
    and advance your career. Get an incredible 1,500+ hours of step-by-step
    tutorial videos with LearnDevNow. Subscribe today and save!
    http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
    _______________________________________________
    Geoserver-users mailing list
    Geoserver-users@lists.sourceforge.net
    https://lists.sourceforge.net/lists/listinfo/geoserver-users
    
------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

6

Ohh, I guess now I got the issue: You are talking about used layer names the user typed in, right? I assume it has nothing to to with static UI elements like table headers, descriptions and so on.

Let me cross check with special German in Workspace names …

I used “ÄÜoderßtest”
as a Workspace name and created it successful. After I selected it in the table (displayed correctly in the column ‘Name’) the following exception occurs:

Arbeitsbereich “ÄÜoderßtest” konnte nicht gefunden werden

which means 'Could not find workspace “ÄÜoderßtest” ’

Seems its a bug, could you create an issue and describe the workflow which leads right into an error

  • Frank
···

2013/9/3 Koivusalo, Tuomas <tuomas.koivusalo@anonymised.com>

Hi,

It seems that most of the files are in us-ascii encoding, layer featuretype.xml’s are for some part in utf-8 (by quickly glancing through list I’d say that layers containing Scandinavian letters are in UTF-8, otherwiser us-ascii). None of the properties files seem to be in UTF-8.

My browser is configured to use English.

I’m downloading 2.4-RC1 right now, I’ll check if I can replicate issue there.

Br,

Tuomas Koivusalo

-----Original Message-----
From: frank.gasdorf@anonymised.com [mailto:frank.gasdorf@anonymised.com] On Behalf Of Frank Gasdorf
Sent: 3. syyskuuta 2013 15:39
To: Koivusalo, Tuomas; geoserver
Subject: Re: [Geoserver-users] Possible regression in encoding handling in Geoserver 2.3.5

Just an additional question : Which language have you configured in you browser? Makes it easier to find the problematic file :wink:

Thanks

  • Frank

2013/9/3 Frank Gasdorf <fgdrf@anonymised.com…>

There was an issue and it should be fixed since 2.3.1 (http://jira.codehaus.org/browse/GEOS-5641) Wondering what has been changed since…

Could you please check the properties file encodings. I may be that some files are UTF-8 I guess.

Have you tried with 2.4-RC1 - same probem here?

  • Frank

2013/9/3 Koivusalo, Tuomas <tuomas.koivusalo@anonymised.com>

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

Learn the latest–Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk

Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

7

I guess same behavior for Workspace names. On file system the name of the workspace folder definitely differs from the name typed into form field.

Its worth to create an issue for each I guess. I’ll create one for the workspace problem later …

Cheers

  • Frank
···

2013/9/3 Koivusalo, Tuomas <tuomas.koivusalo@anonymised.com>

Hi,

It would seem like 2.4-RC1 suffers from same issue. It looks like encoding is changed to UTF-8 if I try to enter ä or ö to title, causing the problem. I checked layer xmls with file -bi before and after testing it.

-Tuomas

-----Original Message-----
From: Koivusalo, Tuomas [mailto:tuomas.koivusalo@anonymised.com]
Sent: 3. syyskuuta 2013 15:46
To: fgdrf@anonymised.com; geoserver
Subject: Re: [Geoserver-users] Possible regression in encoding handling in Geoserver 2.3.5

Hi,

It seems that most of the files are in us-ascii encoding, layer featuretype.xml’s are for some part in utf-8 (by quickly glancing through list I’d say that layers containing Scandinavian letters are in UTF-8, otherwiser us-ascii). None of the properties files seem to be in UTF-8.

My browser is configured to use English.

I’m downloading 2.4-RC1 right now, I’ll check if I can replicate issue there.

Br,

Tuomas Koivusalo

-----Original Message-----
From: frank.gasdorf@anonymised.com [mailto:frank.gasdorf@anonymised.com] On Behalf Of Frank Gasdorf
Sent: 3. syyskuuta 2013 15:39
To: Koivusalo, Tuomas; geoserver
Subject: Re: [Geoserver-users] Possible regression in encoding handling in Geoserver 2.3.5

Just an additional question : Which language have you configured in you browser? Makes it easier to find the problematic file :wink:

Thanks

  • Frank

2013/9/3 Frank Gasdorf <fgdrf@anonymised.com…>

There was an issue and it should be fixed since 2.3.1 (http://jira.codehaus.org/browse/GEOS-5641) Wondering what has been changed since…

Could you please check the properties file encodings. I may be that some files are UTF-8 I guess.

Have you tried with 2.4-RC1 - same probem here?

  • Frank

2013/9/3 Koivusalo, Tuomas <tuomas.koivusalo@anonymised.com>

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

Learn the latest–Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk

Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Learn the latest–Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk

Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users