AlliedModders - REST in Pawn 1.3 - HTTP client for JSON REST APIs (Updated 2021/08/22)

AlliedModders (https://forums.alliedmods.net/index.php)

- Extensions (https://forums.alliedmods.net/forumdisplay.php?f=134)

- - REST in Pawn 1.3 - HTTP client for JSON REST APIs (Updated 2021/08/22) (https://forums.alliedmods.net/showthread.php?t=298024)

Re: REST in Pawn 1.2 - HTTP client for JSON REST APIs (Updated 2021/02/07)

i have sv_hibernate_when_empty always at 0, with this extension my server goes in hibernation like -> sv_hibernate_when_empty 1

edit: it's not the extension, its eitems.smx or estickers.smx

Re: REST in Pawn 1.3 - HTTP client for JSON REST APIs (Updated 2021/06/06)

Version 1.3 has been released with the following changes:

Deprecated HTTPClient methodmap
Introduced HTTPRequest methodmap
Added ability to append query parameters to the URL
Added ability to set the credentials for HTTP Basic authentication
Added ability to set the maximum number of redirects to follow
Added ability to POST form data
Allow user defined 'Accept' and 'Content-Type' headers (thanks Peak)
Fixed HTTP/2 timeouts by enforcing HTTP/1.1 for file transfers on Windows
Fixed response body being printed to server console during file upload
Throw an error when passing empty values to some natives

Download

Re: REST in Pawn 1.3 - HTTP client for JSON REST APIs (Updated 2021/06/06)

Is it possible to log request?

When I try to send some POST data to my API (Laravel), backend receives empty request (headers and method are correct, but there is no POST data).

Code:

    JSONObject BanJson = new JSONObject();

    BanJson.SetString("nickname", Nickname);

    BanJson.SetString("steam_id", SteamId);

    BanJson.SetInt("type", Type);

    BanJson.SetInt("duration", Duration);

    BanJson.SetString("reason", Reason);

    BanJson.SetString("admin_nickname", AdminNickname);

    BanJson.SetString("admin_steam_id", AdminSteamId); 



    HTTPRequest Request = new HTTPRequest(GetApiURI(ApiEndPoint));

    

    Request.SetHeader("Authorization", "Bearer %s",  GeneralConfig.Token);

    Request.SetHeader("GameServer", "%d", GeneralConfig.ServerId);

    Request.SetHeader("Content-Type", "application/json");

    Request.SetHeader("Accept", "application/json");



    Request.Post(BanJson, OnPlayerBan);

Same request sended by PostMan works correctly...

Re: REST in Pawn 1.3 - HTTP client for JSON REST APIs (Updated 2021/06/06)

How are you reading the POST data in Laravel? This works for me with both Postman and REST in Pawn:

PHP Code:


		
			
Route::post('/post', function (Request $request) {
    return new JsonResponse($request->all());
});

Re: REST in Pawn 1.3 - HTTP client for JSON REST APIs (Updated 2021/06/06)

Laravel:

PHP Code:


		
			
Route::post('/test', function (Request $request) {
    return response()->json($request->all());
});

Simple PHP:

PHP Code:


		
			
<?php

$postData = json_encode($_POST);
$jsonData = file_get_contents('php://input');

echo $postData;
echo $jsonData;

file_put_contents('post.txt', $postData);
file_put_contents('json.txt', $jsonData);

?>

Both solutions receives nothing when requesting from game server.

@edit:

PHP Code:


		
			
    Request.AppendFormParam("test", "%s", "foo");
    Request.PostForm(OnTestRequest);

I've used PostForm instead of Post but i still don't know why Post + JSON doesn't work...

@edit-2:
I've saved some backend logs:
PostForm():

PHP Code:


		
			
[2021-06-08 14:39:05] local.DEBUG: Content-Type: "application\/x-www-form-urlencoded"  
[2021-06-08 14:39:05] local.DEBUG: Accept: "application\/json"  
[2021-06-08 14:39:05] local.DEBUG: Path: "api\/test2"  
[2021-06-08 14:39:05] local.DEBUG: Method: "POST"  
[2021-06-08 14:39:05] local.DEBUG: Data: {"test":"foo"}  
[2021-06-08 14:39:05] local.DEBUG: $_POST: {"test":"foo"}

Post() + JSON

PHP Code:


		
			
[2021-06-08 14:41:40] local.DEBUG: Content-Type: "application\/json"  
[2021-06-08 14:41:40] local.DEBUG: Accept: "application\/json"  
[2021-06-08 14:41:40] local.DEBUG: Path: "api\/test2"  
[2021-06-08 14:41:40] local.DEBUG: Method: "POST"  
[2021-06-08 14:41:40] local.DEBUG: Data: []  
[2021-06-08 14:41:40] local.DEBUG: $_POST: []

Post() + JSON (Content-Type: application/x-www-form-urlencoded)

PHP Code:


		
			
[2021-06-08 14:42:42] local.DEBUG: Content-Type: "application\/x-www-form-urlencoded"  
[2021-06-08 14:42:42] local.DEBUG: Accept: "application\/json"  
[2021-06-08 14:42:42] local.DEBUG: Path: "api\/test2"  
[2021-06-08 14:42:42] local.DEBUG: Method: "POST"  
[2021-06-08 14:42:42] local.DEBUG: Data: []  
[2021-06-08 14:42:42] local.DEBUG: $_POST: []

It will be really nice to log what extension sends to backend (to be sure that isn't extension bug)...

Re: REST in Pawn 1.3 - HTTP client for JSON REST APIs (Updated 2021/06/06)

Quote:

Originally Posted by Deather (Post 2749192)

It will be really nice to log what extension sends to backend (to be sure that isn't extension bug)...

I've attached debug builds for Linux and Windows. It would also be useful to know what webserver you're using (Apache / nginx / Caddy?), and which version.

Laravel should automatically fill the Request object if the Content-Type is application/json. PHP's $_POST variable will only be filled when posting form data.

Re: REST in Pawn 1.3 - HTTP client for JSON REST APIs (Updated 2021/06/06)

i don't know why but after i move to my new VPS the PUT think is not working, always return HTTPStatus_Invalid = 0.

My Old VPS : Plesk Panel (PHP 7.4.20 + Server API FPM/FastCGI)
My New VPS : Cyberpanel (PHP 7.4.20 + Server API LiteSpeed V7.9)

"REST in Pawn" (1.2.3) by Tsunami: Provides HTTP and JSON natives for plugins

i test with Postman it's working, but the plugin always return HTTPStatus_Invalid = 0.

anyone experiencing the same thing?

Re: REST in Pawn 1.3 - HTTP client for JSON REST APIs (Updated 2021/06/06)

i try with Debug builds from you above

PHP Code:


		
			
=== Info: STATE: INIT => CONNECT handle 0xde922140; line 1646 (connection #-5000)

=== Info: Found bundle for host subdomain.domain.com: 0xde9070c0 [can multiplex]

=== Info: Re-using existing connection! (#0) with host subdomain.domain.com

=== Info: Connected to subdomain.domain.com (194.XXX.XX.XX) port 443 (#0)

=== Info: STATE: CONNECT => DO handle 0xde922140; line 1700 (connection #0)

=== Info: http2_send len=194

=== Info: h2 header: :method:PUT

=== Info: h2 header: :path:/api/retakes/76561199145573335

=== Info: h2 header: :scheme:https

=== Info: h2 header: :authority:subdomain.domain.com

=== Info: h2 header: user-agent:sm-ripext/1.3.0

=== Info: h2 header: accept-encoding:deflate, gzip

=== Info: h2 header: accept:application/json

=== Info: h2 header: content-type:applicaton/json

=== Info: http2_send request allowed 1 (easy handle 0xde922140)

=== Info: Using Stream ID: 3 (easy handle 0xde922140)

==> Send header
PUT /api/retakes/76561199145573335 HTTP/2

Host: subdomain.domain.com

user-agent: sm-ripext/1.3.0

accept-encoding: deflate, gzip

accept: application/json

content-type: applicaton/json




=== Info: STATE: DO => DO_DONE handle 0xde922140; line 1935 (connection #0)

=== Info: STATE: DO_DONE => PERFORM handle 0xde922140; line 2056 (connection #0)

=== Info: http2_send len=306

=== Info: data_source_read_callback: returns 306 bytes stream 3

=== Info: http2_send returns 306 for stream 3

==> Send data
{"pistolround_ct": "weapon_usp_silencer", "primary_ct": "weapon_ak47", "secondary_ct": "weapon_usp_silencer", "smg_ct": "weapon_ump45", "awp_ct": 0, "scout_ct": 0, "pistolround_t": "weapon_glock", "primary_t": "weapon_ak47", "secondary_t": "weapon_glock", "smg_t": "weapon_ump45", "awp_t": 0, "scout_t": 0}
=== Info: h2_process_pending_input: All data in connection buffer processed

=== Info: data_source_read_callback: returns 0 bytes stream 3

=== Info: http2_recv: easy 0xde922140 (stream 3) win 33554278/33554432

=== Info: nread=13

=== Info: on_frame_recv() header 3 stream 3

=== Info: Got frame type 3 for stream 3!

=== Info: on_stream_close(), PROTOCOL_ERROR (err 1), stream 3

=== Info: Removed stream 3 hash!

=== Info: h2_process_pending_input: All data in connection buffer processed

=== Info: http2_recv: easy 0xde922140 (stream 0) win 33554278/4294967295

=== Info: h2_process_pending_input: All data in connection buffer processed

=== Info: HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1)
*********&#1928;***************************    %******************ܠ******************P*********************************************`*************************** ***************************p***************************,***************************H***************************蠓*********************************************|******************************************************<***************************Ǥ*********ވ***************************`***************************@!******************@Ȓ*********X***************************R***************************
=== Info: multi_done

=== Info: stopped the pause stream!

=== Info: Connection #0 to host subdomain.domain.com left intact

=== Info: Expire cleared (transfer 0xde922140)

Re: REST in Pawn 1.3 - HTTP client for JSON REST APIs (Updated 2021/06/06)

It is possible to send non-chunked request body? Sometimes for shared web-hostings it breaks everything, unfortunately.

Re: REST in Pawn 1.3 - HTTP client for JSON REST APIs (Updated 2021/06/06)

Quote:

Originally Posted by CrazyHackGUT (Post 2754381)

It is possible to send non-chunked request body? Sometimes for shared web-hostings it breaks everything, unfortunately.

Have you tried

PHP Code:


		
			
request.SetHeader("Transfer-Encoding", "");

? I'm not sure if it will work, since it puts a space after the colon.