[CITE-Forum] EXTERNAL:Re: [CITE.SC] beta TEAM Engine updated 2010-09-21

Morris, Chuck E (IS) chuck.morris at ngc.com
Wed Sep 29 12:43:00 EDT 2010


> Using application/xml is always safer.

That may be, but OWS Common mandates using text/xml.

-----Original Message-----
From: cite-forum-bounces+chuck.morris=ngc.com at lists.opengeospatial.org
[mailto:cite-forum-bounces+chuck.morris=ngc.com at lists.opengeospatial.org
] On Behalf Of Richard Martell
Sent: Wednesday, September 29, 2010 11:34 AM
To: Kevin Stegemoller; cite-forum at lists.opengeospatial.org
Subject: EXTERNAL:Re: [CITE-Forum] [CITE.SC] beta TEAM Engine updated
2010-09-21



Using text/xml can be perilous. As stipulated in RFC 3023, the 
default encoding for this media type is US-ASCII:

"if a text/xml entity is received with the charset parameter 
omitted, MIME processors and XML processors MUST use the default 
charset value of "us-ascii".

<http://tools.ietf.org/html/rfc3023#section-3.1>


Using application/xml is always safer.


--
Richard
 

> -----Original Message-----
> From: 
> cite-forum-bounces+rmartell=galdosinc.com at lists.opengeospatial
> .org 
> [mailto:cite-forum-bounces+rmartell=galdosinc.com at lists.openge
> ospatial.org] On Behalf Of Kevin Stegemoller
> Sent: Wednesday, 29 September, 2010 09:16
> To: cite-forum at lists.opengeospatial.org
> Subject: Re: [CITE-Forum] [CITE.SC] beta TEAM Engine updated 
> 2010-09-21
> 
> 
> Jeroen solved his issue. Below is the conclusion of the issue 
> which we 
> took off-list.
> 
> Do any others have any issue with the beta engine.  We would 
> like to use 
> it as the base for the production CITE engine tomorrow.
> 
> Thanks,
> 
> kevin
> 
> On 09/29/2010 11:18 AM, Jeroen Dries wrote:
> > Hi,
> >
> > the issue is indeed caused on our side: we do encode the result as
> > UTF-8 but we do not correctly specify this in the http 
> headers of the
> > response. So we used to give a response with headers like this:
> >
> > Response headers:
> > HTTP/1.1 200 OK
> > Content-Type: text/xml
> > Content-Length: 8282
> > Server: Jetty(6.1.21)
> >
> > HTTPSampleResult fields:
> > ContentType: text/xml
> > DataEncoding: ISO-8859-1
> >
> > After a fix in the server it looks like:
> >
> > Response headers:
> > HTTP/1.1 200 OK
> > Content-Type: text/xml; charset=utf-8
> > Content-Length: 8282
> > Server: Jetty(6.1.21)
> >
> > HTTPSampleResult fields:
> > ContentType: text/xml; charset=utf-8
> > DataEncoding: utf-8
> >
> > I think this will fix the issue.
> >
> > thanks for the help,
> >
> > Jeroen
> 
> 
> On 09/29/2010 08:54 AM, Andreas Schmitz wrote:
> > Jeroen Dries wrote:
> >
> > Hi,
> >
> >> is there any news on this issue? By looking at the root cause, my
> >> guess would be that the session log is not saved correctly as UTF-8
> >> which results in an XML parsing error when the ViewLog utility
> >> tries to read the session log.
> >
> > can I get my hands on the log file? From looking at the code reading
> > and writing should be encoding safe, so I need to try some
> > systematic debugging ;-)
> >
> > Thanks, Andreas -- l a t / l o n  GmbH Aennchenstrasse 19
> > 53177 Bonn, Germany phone ++49 +228 18496-0          fax ++49 +228
> > 18496-29 http://www.lat-lon.de            http://www.deegree.org
> >
> > * * * * * * * * * * * * * * * * * * * * * * * * * * * * deegree day
> > 2010 http://deegreeday.deegree.org * * * * * * * * * * * * * * * * *
> > * * * * * * * * * * *
> 
> -- 
> -------------------------------------------------------
>   Kevin Stegemoller <kstegemoller at opengeospatial.org>
>   The OGC: Making location count...
>   http://www.opengeospatial.org/contact
> -------------------------------------------------------
> _______________________________________________
> CITE-Forum mailing list
> CITE-Forum at lists.opengeospatial.org
> https://lists.opengeospatial.org/mailman/listinfo/cite-forum
> 

_______________________________________________
CITE-Forum mailing list
CITE-Forum at lists.opengeospatial.org
https://lists.opengeospatial.org/mailman/listinfo/cite-forum



More information about the CITE-Forum mailing list