URL Encoding and the HTTP Client Worker

Das Goravani goravanis at gmail.com
Thu Mar 23 16:47:37 UTC 2023

From what I understand, the body or content part of an HTTP Post command, if URL encoded is requested, would look like this for 3 fields called To, From, and Body


Is this correct?

I am trying to get Twilio to work with the HTTP Client Worker object. 

The fact that it encodes the contents in UTF-8 may be a problem.

I can do Twilio with the HTTP Post command. That is working. 

I would prefer to use the asynchronous client worker object. 

But I can’t get it to work.

HTTP Post URL encodes the contents for you. Worker object does not. 

So I’m URL encoding myself, and putting that into "contents" in the worker object. 

But I’m not getting my text on my phone.

Nor is it calling $completed

Isn’t $completed meant to be in the same object that you made the oHTTP.$start method call?

So if I am working in my startup task then $completed should simply be a method in the startup task. 

Isn’t that right?  I can’t look at the docs right now.. you can’t search them right now.. I tried finding the worker objects refs but could not. 

More information about the omnisdev-en mailing list