Interesting. I would expect a CCSID problem to be much more consistent. Do you remember the content-type the failing responses showed? Did you find a pattern in what responses failed? I'm wondering if I can get the client to extract the garbage that appears before my valid JSON. Did you try that? It might help determine where it's coming from
Thanks
________________________________
From: Steve Richter <stephenrichter@xxxxxxxxx>
Sent: Friday, May 24, 2019 1:36 PM
To: Web Enabling the IBM i (AS/400 and iSeries)
Subject: Re: [WEB400] Garbage in HTTP response
not sure about RPG CGI, but I got this sort of data a lot when sending JSON
from PHP to Javascript. Had to do with translating from EBCDIC to ASCII.
In my case I changed the CCSID of some columns to 1208. ( which actually
might not have been necessary. ) Also had to work with the parameters in
PHP when converting to JSON.
This mailing list archive is Copyright 1997-2024 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.
midrange.com
