On Mon, Jun 4, 2012 at 2:13 PM, Rahkonen Jukka <[email protected]> wrote: > Hi, > > We have some troubles with Geoserver sending out UTF-8 formatted > GetFeatureInfo responses for Windows clients which default to ISO-8859-1. > Our developer said that it would be nice if the response headers came with > charset info, for example by containing something like > <meta http-equiv="content-type" content="text/html; charset=UTF-8"></meta> > > We have been thinking that perhaps we can add charset info be creating a > custom header.ftl file. However, I wonder why Geoserver does not advertise > the charset automatically?
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. 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 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
