Re: http_post equivalent of curl example

Curious why a PASE approach can't be used ?

Just call an RPG or CL that does the real call to curl.

Is the client really against using PASE ?

Curl be so easy 😊

Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx

----------------------------------------------------------------------

message: 1
date: Mon, 15 Jul 2024 13:13:40 -0400
from: Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
subject: Re: http_post equivalent of curl example

no worries Jack - I know you do - I would be too if I weren't needing to
do this type of thing from an old COBOL legacy code base.
so we need a native approach - not even a PASE curl approach would do.

We have resources here that can reach out to Scott F directly if we need to
- so may try that next.

thanks for the effort

Jay

On Mon, Jul 15, 2024 at 12:57?PM Jack Woehr via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

Hmm, I'll have to set up to try it ... Not sure that I'll have time
today ... I'm sure it works ... Maybe you and I could share screen
sometime and play with it ... otherwise I'd have to figure out an
example. I mostly do this stuff in PHP/Python/JS



________________________________
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of
Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
Sent: Monday, July 15, 2024 10:48 AM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: http_post equivalent of curl example

CAUTION: This email originated from outside of the organization. Do
not click links or open attachments unless you recognize the sender
and know the content is safe.

Yes, http_post is... url,body,headers

so leaves only one place to put them... in the body...

I have tried both the json structure in the body...
'{"grant_type": "client_credentials", "client_id": "client_id",
"client_secret": "client_secret"}'


and the string structure... Neither work.
'grant_type=client_credentials, client_id=client_id,
client_secret=client_secret'

--
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@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.