Re: http_post equivalent of curl example

[Jay Vaughn <jeffersonvaughn@xxxxxxxxx>]

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'

Can this even be done with http_post?


Jay





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

> Possibly the POST message instead of
>
> '{"grant_type": "client_credentials", "client_id": "client_id",
> "client_secret": "client_secret"}'
>
> get sent as
>
> 'grant_type=client_credentials, client_id=client_id,
> client_secret=client_secret'
>
> ________________________________
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of
> Jack Woehr via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>
> Sent: Monday, July 15, 2024 10:19 AM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
> Cc: Jack Woehr <jack.woehr@xxxxxxxxxxx>
> Subject: Re: http_post equivalent of curl example
>
> HTTP_POST is url, message, options
>
>
> --
> 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.