makeWebRequest URL with Params

As I mentioned here as a question, there is still one issue with making web requests.

Some webservices contain authentication parameter within the URL. It is not possible to combine them with other parameter.

For example Microsoft Flow or Azure-Functions (Containing a fake sig):
https://prod-45.westeurope.logic.azu...l/paths/invoke?api-version=2016-06-01[/url]&sig=AbCdEfGhIjKlMnOpQrStUvW1234567890

Using this URL, I cannot submit data with "params" in
Comm.makeWebRequest(url, params, options, responseCallback);
It gives me a 401 with parameter and a 400 with null as params. I guess, leaving params null, the authentications works, but the data is missing.

Removing api & sig from the URL and enhance it to the data, it does not work. Neither in header, nor in params.
That's why expect an issue rather then a wrong coding approach. Using Azure Functions without authentication token, the code works fine!

Coleman.Apps over 7 years ago

Hey,

We've got a ticket created and should be looking at this this week.

Thanks,
-Coleman

HerrRiebmann over 7 years ago

Hello Coleman.
is there any update in the ticket?

Thanks and have a nice weekend :)

Travis.ConnectIQ over 7 years ago

HerrRiebmann,

Just to verify, you're trying to do this...

var url = "prod-45.westeurope.logic.azure.com/.../invoke

var params = {
  "sig" => "AbCdEfGhIjKlMnOpQrStUvW1234567890"
};

Comm.makeWebRequest(url, params, options, responseCallback);

If so, the problem is that the query component of the uri is specified entirely by the params dict. If the params dict is not empty, the makeWebRequest() call will append a '?' followed by the key/value pairs from the dict. I believe the final uri for the above request would be

prod-45.westeurope.logic.azure.com/.../invoke

This is not likely to be what you want.

To avoid this problem, you should be specifying all of the query parameters in the params dict. e.g.,

var url = "prod-45.westeurope.logic.azure.com/.../invoke";

var params = {
  "api-version" => "2016-06-01",
  "sig" => "AbCdEfGhIjKlMnOpQrStUvW1234567890"
};

Comm.makeWebRequest(url, params, options, responseCallback);

Does that make sense? Does it not work for you?

HerrRiebmann over 7 years ago

Hi Travis,

I was more clearly in the initial post.
It might work by submitting the parameter via "params". But then you cant submit params :D

The problem is, that you cannot combine the authentication-parameters and add data.

Neither like that:

var url = "prod-45.westeurope.logic.azure.com/.../invoke";
 var params =     {
          "sig" => "bCdEfGhIjKlMnOpQrStUvW1234567890",
          "sp" => "/triggers/manual/run",
          "api-version" => "2016-06-01",
          "sv" => "1.0",
           "device" => "ESP8266MOD",
          "no" => "19",
          "ipAdress" => "192.168.100.19",
          "epoch" => "1500990912"
               };

Nor like this:

var url = "prod-45.westeurope.logic.azure.com/.../invoke  
 var params =     {
          "device" => "ESP8266MOD",
          "no" => "19",
          "ipAdress" => "192.168.100.19",
          "epoch" => "1500990912"
               };

To make it safe, I need both.
Without authentication (token, version, ect.) it works. Or without data (device, no, ip, ect.), also.

Using the header wasn't helpful. as well.