Re: Getting Bad Request from a HTTPAPI call

That is something you'll need to ask Scott.

Our GETURI (www.bvstools.com/geturi.html) software when in debug shows the
headers and body of the request (ie, the complete request) as well as a
complete log of communications in another log file.

Brad
www.bvstools.com

On Thu, May 12, 2016 at 12:35 PM, Shubhadeep Roy <shubhadeep.roy@xxxxxxxxx

wrote:

Thank you Brad and Vernon.

The debug log that I pasted was from the stream file with http_debug-
http_debug(*ON : '/tmp/ShubhDebugLog.txt');

But the log does not show the BODY of the request. Am I missing

something?

Is there any other way to start the debugger?

I had put up this question in Scott's mailing list about 2 weeks back and
also tried to follow up but no one has responded so far.


On Thu, May 12, 2016 at 1:14 PM, Bradley Stone <bvstone@xxxxxxxxx>

wrote:

It's not junk.. it's an ASCII (1208, UTF) representation. You're

viewing

it through your EBCDIC session which is why it looks like garbage.

Can you turn on debug with HTTPAPI and have it save the request to a

stream

file? Then look at that stream file instead to see what the JSON data
looks like.

I also think Scott has mailing lists dedicated to his offerings as well
that you may want to check out.

Brad
www.bvstools.com

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.