On Mon, Jun 4, 2012 at 3:35 PM, Rahkonen Jukka <[email protected]> wrote: >> The header.ftl file it's something that you can modify as you see fit, >> but GeoServer >> does not parse it to see if you declared a charset, so it >> will continue to emit >> GetFeatureInfo in UTF-8. > > We noticed that it may lead to invalid situation too if we have header.ftl > that advertises hard coded UTF-8 but from global server settings the encoding > is changed to something else. However, we plan to use UTF-8 everywhere so > that should work for us.
Aah, right, well, I guess we could make the charset configured in GeoServer injectable into the template so that the two are kept in synch > >> GeoServer does not advertise the charset automatically >> because we don't >> have the code that sets up the headers for GetFeatureInfo >> output I guess. >> Can you open a ticket in Jira? A patch would be nice too :-p > > I can do tickets but not patches but I am not totally alone here. Anyway, I > will start with a ticket. Nice Cheers Andrea -- Ing. Andrea Aime GeoSolutions S.A.S. Tech lead Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 962313 mob: +39 339 8844549 http://www.geo-solutions.it http://geo-solutions.blogspot.com/ http://www.youtube.com/user/GeoSolutionsIT http://www.linkedin.com/in/andreaaime http://twitter.com/geowolf ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
