Henrik,

content-type: text/plain; charset=UTF-8

seems to work fine (the output is readable in the browser / client).

whereas:

content-type: application/xml; charset=UTF-8

does not work (the output is unreadable in the browser / client).

My understanding is that the HTTP server performs NO encoding of output body in Binary mode; The RAW EBCDIC stream is output, so it appears scrambled on the client.

CCSIDs, Code Pages, Conversion Modes, the effect of HTTP configuration directives and headers are all confusing to me. But are we on the same page? 

-Nathan.

.



________________________________
From: Henrik Rützou <hr@xxxxxxxxxxxx>
To: Web Enabling the IBM i (AS/400 and iSeries) <web400@xxxxxxxxxxxx>
Sent: Wednesday, July 3, 2013 2:19 PM
Subject: Re: [WEB400] XML response is getting scrambled


Nathan,

content-type: text/plain; charset=UTF-8

will set the server in BINARY mode

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.