On Tue, Apr 23, 2013 at 10:47 AM, sores <[email protected]> wrote:

> **
>
> Hi Andrea,
>
> Thanks for the response!
>
> In both cases I use Tomcat. I have checked the response with wfetch, and
> Geoserver 1.7.2 behavior is different from Geoserver 2.3.0. The problem
> only occurres when GetFeatureInfo format is text/plain, otherwise charset
> is defined in the html or xml header. Unfortunately, Geonetwork seem to use
> text/plain. However, the root of the problem is the ambiguous output of
> Geoserver.
>
> If there is no way to make Geonetwork assume that the undefined charset is
> UTF-8, is there any workaround for the problem in Geoserver or tomcat?
>
Not that I know of. As said before, I have a hard time considering this a
bug too, I don't remember OGC demanding the charset to be added to the
mime types.

Cheers
Andrea



-- 
==
GeoServer training in Milan, 6th & 7th June 2013!  Visit
http://geoserver.geo-solutions.it for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to