HTTP Post Problem

[Michael Frey]

I have a POST set up with the following data, each on a new line.

username=myname
password=mypass
data=mydata

If I use a content type of text/*, text/plain or text/html the
returned variables are:
%HTTPR: 200
%HTTPL: 42
%HTTPD: missing credentials (username was:)

So somehow the post does not send the data.

If I use the content type: application/x-www-form-urlencoded the
variables are:
%HTTPR: 200
%HTTPL: 23
%HTTPD: %HTTPD

So it seems that the data returned is not read correctly into the
%HTTPD variable.

Is this a bug, or how could i fix this?

Michael

[Pent]

> I have a POST set up with the following data, each on a new line.
>
> username=myname
> password=mypass
> data=mydata

Are you trying to use the basic authorization scheme ?

Pent

[himanshu patel]

I am Not getting the Question exactly

Can you please elaborate?

Regards

Himanshu

[Michael Frey]

No it's not authentication. The website is an API for sending sms and
it requires that information, but it is not actual authentication in
the sense of ssl or logging in.

[Michael Frey]

I will elaborate on this.

The url is an API for sending SMS through a server. The response is
supposed to be something like: 1|cost=1.5

But it refuses to return that specific message, due to the problems
described in my original post.

[Pent]

> If I use the content type: application/x-www-form-urlencoded the
> variables are:
> %HTTPR: 200
> %HTTPL: 23
> %HTTPD: %HTTPD

You can write it to a file (using the parameter in the HTTP Post
action), then read it back with File / Read Line. It's because Tasker
isn't sure the content is text so won't put it in a text variable.

Pent

[Michael Frey]

That works. This would be a good feature on the HTTP setup screen.
Include a checkbox to force the post to accept the response as text.

Michael