Thanks again Narinder. Indeed, XSLT is going away.
I think what I’ve put together with Miyako’s encoding component and some hard-coded concatenation will be sufficient for this one time, non-scalable, semi-hack. ;) If I need to do it more than once I’ll look at doing it the “right” way. I appreciate all the suggestions you’ve offered. Tom Benedict > On Oct 12, 2019, at 15:50, Narinder Chandi via 4D_Tech <[email protected]> > wrote: > > Tom, > > This may have been mentioned already, but I just remembered that it is > possible to do this encoding natively with 4D's XML and XSLT Transformation > commands and I wrote a pair of encode/decode functions several years ago that > worked no problem. > > However, XSLT has been deprecated in v17. So, unless you are using a prior > version of 4D (and I get the impression that you are not as you mention ORDA > in a previous post) then you are out of luck. However, if you want the > encode/decoded functions let me know and I can send them to privately. > > 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 23:12 > To: 4D Tech Mailing List <[email protected]> > Cc: Narinder Chandi <[email protected]> > Subject: Re: HTTP Request and x-www-form-urlencoded > > Tom, > >> 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. > > Unfortunately HTTP Request is sadly still lacking this capability and, to > the best of my knowledge, it is not a part of the HTTP client command set or > the Internet Command set which is rather a glaring oversight IMO. It is > pretty standard stuff as far as HTTP requests go. 4D really need to address > this. > > You could perhaps create your own wrapper around HTTP Request and combine > that with Miyako's code if that might solve your problem? > > 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 > -- > > > > ********************************************************************** > 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] **********************************************************************
