I have implemented an even better solution so that platforms using a non-UTF-8 default charset *will* be able to support characters outside of this charset in a WFS KVP Filter:
[GEOS-7385] Do not re-encode Filter in default charset when parsing WFS KVP Filter https://github.com/geoserver/geoserver/pull/1449 https://osgeo-org.atlassian.net/browse/GEOS-7385 Kind regards, Ben. On 23/01/16 14:26, Ben Caradoc-Davies wrote: > Nhan Vo, > > I think you are not only correct but have located the culprit. I was > able to reproduce the problem for both "ü*" and "Ü*" if I run GeoServer > with -Dfile.encoding=ISO-8859-15 and try the two links you provided > earlier. I have documented this failure and how to reproduce it in a > Jira issue: > https://osgeo-org.atlassian.net/browse/GEOS-7385 > > I was so pleased by your detailed report that I wrote a unit test to > demonstrate the failure and also a fix, which I have submitted in this > pull request: > https://github.com/geoserver/geoserver/pull/1446 > > Note that, even with this fix, platforms using a non-UTF-8 default > charset will not be able to support characters outside their charset in > a WFS KVP Filter. > > Kind regards, > Ben. -- Ben Caradoc-Davies <[email protected]> Director Transient Software Limited <http://transient.nz/> New Zealand ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
