Status Stack Buffer Overrun

[lmarschall]

As i progress, using the Addon to establish an authorization workflow, i now stumbled across the following error:
"0xC0000409 - STATUS_STACK_BUFFER_OVERRUN".

Here's my request:

_cliendid = ["http://192.168.0.102:8000/api/user", "GET", [], true] call a3uf_common_fnc_addClient;

access_token = "7c9f8d58da05147b9cfe0bfb9210603668c924bc";

_token_string = format ["Bearer %1", access_token];

[_cliendid, [["Content-Type", "application/json"], ["Authorization", _token_string]]] call a3uf_common_fnc_setClientHeaders;

_response = [_cliendid] call a3uf_common_fnc_clientRequest;

Its a function, spawned by user input, which calls a local api endpoint, maybe its just a headers problem.

Thanks in advance,

Luke

[pixlcrashr]

I'll have a look into it. That seems like an error referring to the library, though.

[pixlcrashr]

this may be the cause: https://github.com/playnet-public/ArmA3URLFetch/blob/master/src/clients.cpp#L62

Later on I'll provide a library that you can test for that error.

[lmarschall]

Ok i think i can specify the error, it seems like no header was added to the request.

[pixlcrashr]

Ok i think i can specify the error, it seems like no header was added to the request.

Is it being added when using a normal request without any client? You may check this by calling http://httpbin.org/get.

[lmarschall]

can you set headers without a client session?

[lmarschall]

so i figured it out now!

it was indeed a headers problem, my request didnt work with the given headers array.
Here's my functional request with working headers:

_cliendid = ["http://192.168.0.102:8000/api/user", "GET", [], true] call a3uf_common_fnc_addClient;

_auth_string = format ["Authorization: Bearer %1", access_token];

[_cliendid, ["Content-Type: application/json", _auth_string]] call a3uf_common_fnc_setClientHeaders;

_response = [_cliendid] call a3uf_common_fnc_clientRequest;

So the original error was only the result of my api endpoint didnt know what to do with the given request and returning an error.

[pixlcrashr]

@lmarschall Good job! I may update the Wiki description, though.

Btw. it is therefore possible to append headers to a normal request (was missing in the docs). The parameters are as follows:

params [
	["_url", "", [""]],
	["_method", "", [""]],
	["_headers", [], [[]]],
	["_postData", "", ["", []]],
	["_decodeJson", false, [false]]
];

.

Indeed, the current Wiki description does not inlcude the _headers param.

[lmarschall]

maybe one addition, when the api endpoint sends a 400 status code, bad request, the addon crashes the game with the original error from above, maybe there's a way to handle such errors in the addon, so the game is not influenced by such bad requests.

[pixlcrashr]

maybe one addition, when the api endpoint sends a 400 status code, bad request, the addon crashes the game with the original error from above, maybe there's a way to handle such errors in the addon, so the game is not influenced by such bad requests.

I'll check it out.

[lmarschall]

so i created a framework for accessing player information in multiplayer missions from an api endpoint with your addon as work horse, would be interesting to get your feedback if that's a good idea over all: https://forums.bohemia.net/forums/topic/231816-accessing-player-data-from-api-endpoint/

Best Regards,

Luke