Hi Narinder,

Thanks again for your quick response!

>I'm not sure but maybe this will help you?
> 
> >https://github.com/miyako/4d-tips-encode-uri 
> ><https://github.com/miyako/4d-tips-encode-uri>
I found that component earlier today and it does help a bit. I was looking for 
a way to fill an object with key value pairs which HTTP Request would then 
convert into the right content-type. 

Tom Benedict

> On Oct 12, 2019, at 13:45, Narinder Chandi via 4D_Tech <[email protected]> 
> wrote:
> 
> Tom,
> 
> I'm not sure but maybe this will help you?
> https://github.com/miyako/4d-tips-encode-uri
> 
> Regards,
> 
> Narinder Chandi,
> ToolBox Systems Ltd.
> 
> I am available for new consulting opportunities…
> http://4d.1045681.n5.nabble.com/ANN-4D-Developer-Available-td5765443.html
> -- 
> 
> -----Original Message-----
> From: 4D_Tech <[email protected]> on behalf of 4D Tech Mailing 
> List <[email protected]>
> Reply-To: 4D Tech Mailing List <[email protected]>
> Date: Saturday, 12 October 2019 at 20:54
> To: 4D Tech Mailing List <[email protected]>
> Cc: Tom Benedict <[email protected]>
> Subject: HTTP Request and x-www-form-urlencoded
> 
>    I have very little experience with HTTP Request. I’m calling an external 
> REST service using 4D’s HTTP Request command. The REST service requires that 
> the content-type be x-www-form-urlencoded. The “contents” parameter of the 
> HTTP Request command supports sending a 4D Object (JSON) but that is failing 
> (unknown parameter) when I submit it to the REST service. I suspect that is 
> the REST service is expecting x-www-form-urlencoded rather than JSON. 
> 
>    I’ve successfully tested the REST service using Postman and I can copy the 
> encoded URL from Postman and send it successfully from 4D HTTP Request 
> instead or JSON. So I just need to build the encoded URL on the 4D side. It’s 
> tedious to do though, and I think it’s convenient to use an object on the 4D 
> side to manage the key value pairs. So I’m wondering is there an ‘easy’ way 
> to convert a JSON object into an encoded URL?
> 
>    Hope this makes sense,
> 
>    Tom Benedict
>    **********************************************************************
>    4D Internet Users Group (4D iNUG)
>    Archive:  http://lists.4d.com/archives.html
>    Options: https://lists.4d.com/mailman/options/4d_tech
>    Unsub:  mailto:[email protected]
>    **********************************************************************
> 
> 
> **********************************************************************
> 4D Internet Users Group (4D iNUG)
> Archive:  http://lists.4d.com/archives.html
> Options: https://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:[email protected]
> **********************************************************************

**********************************************************************
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[email protected]
**********************************************************************

Reply via email to