Re: Help With Getting HTTP Server running

How are you reading it in? That's what I'm probably "missing" haha.

If you're using the YAJL function, or even just QtmhRdStin, I've never seen
the data encoded as a POST.


Bradley V. Stone
www.bvstools.com
MAILTOOL Benefit #13 <https://www.bvstools.com/mailtool.html>: The ability
to use an IFS stream file as the body of the email (either text or html).

On Thu, Feb 14, 2019 at 10:35 AM Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
wrote:

well i just tried doing a POST instead of a GET with the exact same
criteria and it came across encoded as well...

so something you are missing Brad...

but I am good from here - thanks to all that helped me with this.

Jay

On Thu, Feb 14, 2019 at 11:33 AM B Stone <bvstone@xxxxxxxxx> wrote:

Or you just just make it a POST and save some work. :)

Bradley V. Stone
www.bvstools.com
MAILTOOL Benefit #2 <https://www.bvstools.com/mailtool.html>: The

ability

to specify a "From" and/or "Reply To" email address!

On Thu, Feb 14, 2019 at 10:31 AM Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
wrote:

here is how i'm going to deal with it so that the front end guy is not
burdened with it...

in my rpgle pgm..

EVAL jsonINP
jsonINP =
....5...10...15...20...25...30...35...40...45...50...55...60
1 '%7B%22env%22:%22D3X%22,%22command%22:%22GET_L'
61 'OAN_BORROWER%22,%22payload%22:[%7B%22loanNumber%22:2428%7D]%'
121 '7D


jsonINP = %scanrpl('%7B'
:'{'
:jsonINP);

jsonINP = %scanrpl('%7D'
:'}'
:jsonINP);

jsonINP = %scanrpl('%22'
:'"'
:jsonINP);

and wala...

EVAL jsonINP
JSONINP =
....5...10...15...20...25...30...35...40...45...50...55...60
1 '{"env":"D3X","command":"GET_LOAN_BORROWER","payload":[{"loan'
61 'Number":2428}]}


sometimes just not worth the risk of leaving it up to others.. and
considering the fact i'm using a rather unorthodoxed way with this

whole

process I better assume that responsibilty...

now last thing is to have the YAJL produce back out the generate json
output and I'm done!

Jay







On Thu, Feb 14, 2019 at 11:09 AM Nadir Amra <amra@xxxxxxxxxx> wrote:

You have to deal with the decoding, that is part of the HTTP standard

with

regards to what characters may be specified on a URL. So browser

encodes

before sending.






"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on

02/14/2019

09:47:58 AM:

From: Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
To: Midrange Systems Technical Discussion

<midrange-l@xxxxxxxxxxxxxxxxxx>

Date: 02/14/2019 09:57 AM
Subject: Re: Help With Getting HTTP Server running
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>

thanks Bradley - still not quite what i'm looking for...

i think i may just about have it with the SK yahlserver setup...

so I can now reach my endpoint...

my iseries YAJL pgm gets called but there seems to be some encoding

going

on that is throwing off my json string...

This is what I'm calling from ARC using the GET method...

/rest/wsr00000/{"env":"D3X","command":"GET_LOAN_BORROWER","payload":

[{"loanNumber":2428}]}

in debug over on the i, I get this interpretation of it...

EVAL l_url
L_URL =

....5...10...15...20...25...30...35...40...45...50...55...60

1

'/rest/wsr00000/%7B%22env%22:%22D3X%22,%22command%22:%22GET_L'

61

'OAN_BORROWER%22,%22payload%22:[%7B%22loanNumber%22:2428%7D]%'

121 '7D

how can I preserve the original string format of the json input?

Ive tried enclosing the json input string in single quotes but no

luck.

I've also tried an escape version of the string with no luck...
{\"env\":"D3X",\"command\":\"GET_LOAN_BORROWER\",\"payload\":
[{\"loanNumber\":2428}]}


any suggestions? almost there!

Jay

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our

affiliate

link: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com