Re: Garbage in HTTP response

Justin

The HTTP server will normally convert EBCDIC to ASCII for certain content
types. application/<anything here> is not one of them.

For example, if you go to the DSPJSON example here:
http://erpgsdk.bvstools.com/

You'll see that for the eRPG SDK we specifically need to be able to set the
CCSID of the output so things would work.

Other "fixes" tried are text/json, but that's not the proper content type
for JSON.

You'll see how


Bradley V. Stone
www.bvstools.com
MAILTOOL Benefit #16 <https://www.bvstools.com/mailtool.html>: No external
"helper" PC system required. 100% IBM i native!

On Sat, May 25, 2019 at 2:02 PM Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

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 is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.