-
Notifications
You must be signed in to change notification settings - Fork 37
Can't get POST request data #163
Comments
Hello @Al-Muhandis . I'm not sure about you are using in the client-side, but it seems you just need to inform the content-type. For example, if you are using fphttpclient (FPC) or NetHTTPClient (Delphi), just: YourClient.ContentType := 'application/json'; |
Additional info (that will be documented soon):
|
|
The procedure I have is performed inside the |
Could you test it outside the webhook using |
Good news: you can use any HTTP method in the Tardigrade broker. :-)
They are available in the request object of Brook 5+, however, in legacy apps, you can debug to check if I've tested all features before releasing v4.0.0, but I'll retest them again tonight. |
The same... Empty POST data in the request |
Confirmed. I'm going to check it tonight and provide a patch fixing the problem. Thanks for reporting! |
@Al-Muhandis , could you try this attached experimental patch? To apply it, download Brook here, the patch 0001 and 0002, so: git apply 0001-Removes-redundant-configuration.patch
git apply 0002-Fix-issue-161-high-CPU-activity-in-Tardigrade-based-.patch
git apply 0003-Fix-issue-163-reported-by-Al-Muhandis.patch.txt and rebuild your application again to test if it works. It is experimental, but should work well. |
Thank You very much! I applied the 2nd patch even earlier. 3rd patch just now. Now everything works! |
So now I can clarify that telegram plugin does not work with tardigrade broker without 3 patch for BF 4.0 |
Indeed. Tonight I'm going to do some tests and move this patch to here. :-) |
Done! Thanks @Al-Muhandis ! 😃 |
Can't get POST request data.
Legacy app 4.0.0 with tardigrade. Debian. Post data is not fields, that is string JSON Data.
Before with THTTPDaemonBroker worked
The text was updated successfully, but these errors were encountered: