Hi, The Content-Type header returned by the server does not include the encoding. I *think* it that case the one set in the XML declaration (that is, on the first line of the content: "<?xml ...") should be taken into account.
If the server you consume from is yours, I would strongly recommend to set the encoding in the Content-Type header. Regards, -- Florent Georges http://fgeorges.org/ http://h2o.consulting/ - New website! On 14 October 2017 at 21:17, Zakiya Tamimi wrote: > <headers> > <content-type>text/xml</content-type> > <last-modified>Thu, 20 Jul 2017 07:35:19 GMT</last-modified> > <accept-ranges>bytes</accept-ranges> > <etag>"1a67d5bc2a1d31:0"</etag> > <server>Microsoft-IIS/8.0</server> > <x-powered-by>ASP.NET</x-powered-by> > <date>Sat, 14 Oct 2017 19:11:29 GMT</date> > <content-length>83144</content-length> > </headers> > > > On Sat, Oct 14, 2017 at 3:32 PM, Florent Georges <[email protected]> > wrote: > >> Hi, >> >> You use an HTTP source. What are the returned headers, esp. the >> Content-Type? You can find out easily in QConsole by using xdmp:http-get(). >> >> Regards, >> >> -- >> Florent Georges >> http://fgeorges.org/ >> http://h2o.consulting/ - New website! >> >> >> On 14 October 2017 at 12:48, Zakiya Tamimi wrote: >> >>> I have posted my question at stackoverflow >>> https://stackoverflow.com/questions/46722188/marklogic-encod >>> ing-xdmpdocument-load >>> >>> Here's the text of the question: >>> >>> I have noticed that utf-8 xml documents loaded (xdmp:document-get() + >>> xdmp:document-insert()) into our development marklogic server (7.0-6.8) >>> have ascii encoding. Meanwhile back on production server (7.0-5.1), there >>> is no problem; utf-8 is loaded as utf-8. I traced the problem and found it >>> to be caused by xdmp:document-get(). >>> >>> So I wrote the following code snippet and ran it on both server consoles >>> and got incorrect encoding on the development server and correct encoding >>> on production. >>> >>> let $options := <options xmlns="xdmp:document-get"> >>> <repair>full</repair> >>> <encoding>UTF-8</encoding> >>> <format>xml</format> >>> </options> >>> let $url := "http://******/ref_batches/electronic/20170801_e31_004 >>> /201731780-004.xml" >>> return xdmp:document-get($url, $options) >>> >>> My initial guess: different version numbers may have caused this. So I >>> tested on a local server (7.0-6-12) and got correct utf-8 encoding. Later >>> we upgraded our development server to (7.0-6-12) and re-tested to get >>> incorrect encoding (ascii) >>> >>> Is there some marklogic configurations that are responsible for this >>> trans-coding? >>> >>> Thanks >>> >>> >>> >>> _______________________________________________ >>> General mailing list >>> [email protected] >>> Manage your subscription at: >>> http://developer.marklogic.com/mailman/listinfo/general >>> >>> >> >> >> >> >> >> _______________________________________________ >> General mailing list >> [email protected] >> Manage your subscription at: >> http://developer.marklogic.com/mailman/listinfo/general >> >> > > _______________________________________________ > General mailing list > [email protected] > Manage your subscription at: > http://developer.marklogic.com/mailman/listinfo/general > >
_______________________________________________ General mailing list [email protected] Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
