Skip to content

Parameters

Vincent Heins edited this page Feb 25, 2019 · 4 revisions

Parameters

In ArmA3URLFetch there are two kinds parameters: custom- and predefined parameters.
A parameter is made of two variables: A predefined <id> and a <value>.

Parameter format:

<id>=<value> this is the default format for your parameter(s).
Every custom value is transmitted as a HTTP form.

Predefined parameters:

According to interact with the extension, there a some predefined parameters/id's.
#url is one of the id's.
Predefined parameters always start with a '#'. Of course you can use this char in your custom id's.

Custom parameters:

Custom parameters are your own parameters send by the extension to the receiving HTTP host.
A custom parameter can be literally anything except predefined parameters.
myCoolID=myTestString is a valid parameter whilst
#url=AnotherCoolString is not!

In the end your custom parameters will automatically added by the extension to the #url like this:
https://httpbin.org/get?myCoolID=myTestString&<id>=<value>&...

Predefined parameters list

ID Description Value
#url This is the URL of your wanted request. You simply insert your URL as <value>. You may have to check if your URL is correct specified. <string>
#method This is the method of the request. It can be POST, GET, PUT, DELETE, PATCH and TRACE. More about HTTP methods here. <string>
#jsonToArray If you await a result in JSON format (like from a RESTAPI), you can decode that object with this command to an ArmA 3 friendly array.
As callExtension only returns strings, you have to use parseSimpleArray on the result to get an ArmA 3 readable array.
This command applies if attached to the arguments.
None.

That's it for now.

Clone this wiki locally