HTTP Request Node JSON body error

[qkxie]

Self Checks

• [X] This is only for bug report, if you would like to ask a question, please head to Discussions.
• [X] I have searched for existing issues search for existing issues, including closed ones.
• [X] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• [X] Please do not modify this template :) and fill in all the required fields.

Dify version

0.10.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

1. create a http request node
2. set request method to post, and set body to json
3. make a request

✔️ Expected Behavior

get the response

❌ Actual Behavior

http request node change my json body. the field of top_k should be 8, but in the log, it becomes to null, so the request failed.

[dosubot[bot]]

I found two similar discussions regarding issues with the HTTP request node losing JSON request data:

1. The HTTP-request node loses JSON request data after I saved it, last updated on May 8, 2024.
2. HTTP request node 填写了 body，保存完后，还是 none 选项，填写的json丢失！！！, last updated on May 6, 2024.

These discussions are still open and unsolved, which might indicate a related issue with how JSON bodies are handled in the HTTP request node.

Regarding your specific issue, it seems that the top_k field in your JSON body is unexpectedly set to null, which causes the request to fail. This could be due to a bug in the handling of JSON bodies in the HTTP request node. There is an error handling mechanism in place that logs warnings if exceptions occur during the execution of the HTTP request node, which might help in diagnosing the issue ^[1].

If you haven't already, you might want to check the logs for any warnings or errors that could provide more insight into why the top_k field is being set to null. Additionally, ensure that the JSON body is correctly formatted and that all variables are properly defined and accessible in the context of the request.

To continue talking to Dosu, mention @dosu.

[qkxie]

You can reproduce this bug by just simply set url to https://xxx.com/a, and set body to

{
"test1": true,
"test2": 5
}

just like below:

[laipz8200]

I think it should be fixed in the main branch by #9616

[qkxie]

As I use docker-compose to launch Dify, should I build a docker image by myself and replace the image url in docker compose yaml? When will you release a new version which include the patch? @laipz8200

[crazywoola]

@qkxie