"The HTTP request in the workflow cannot be saved."

[xiaodong-l]

Self Checks

• This is only for bug report, if you would like to ask a quesion, please head to Discussions.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• Pleas do not modify this template :) and fill in all the required fields.

Dify version

0.6.6

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

"After closing, the HTTP request module in the workflow automatically resets the POST request to GET, and it cannot save the BODY and API authentication."

✔️ Expected Behavior

To address the mentioned issues:

1.Automatic Reset to GET Request: You need to ensure that the workflow or the HTTP request module retains the selected method (POST) even after closing. This might involve checking for any settings or configurations that reset the method to GET upon closure and modifying them accordingly.
2.Inability to Save BODY and API Authentication: You can troubleshoot this by examining the settings related to saving request configurations in the HTTP request module. Ensure that the module supports saving and retrieving request bodies and authentication credentials. If not, you might need to explore alternative modules or custom solutions that provide this functionality.

❌ Actual Behavior

No response

[dosubot]

It seems like the issue you're encountering with the HTTP request module not saving the POST request settings, including the BODY and API authentication, could be related to the way Dify handles HTTP request configurations. This might involve a closer look at the HttpRequestNodeData class within Dify's codebase, which is responsible for defining the structure for these settings. If this class or the system does not properly save these settings to a persistent storage, they would be lost upon restarting the application or closing the workflow.

The problem could also stem from external libraries like httpx and requests that Dify uses for making HTTP requests. Any issues with these libraries might affect the module's functionality. Additionally, Docker environment settings could play a role, especially if there are misconfigurations in network settings, storage, or environment variables that impact the module's ability to save settings.

To troubleshoot, you might want to check for any error logs or messages that could provide more insight into what's going wrong. Also, reviewing Dify's integration tests related to HTTP request configurations might offer clues on how these settings are supposed to be saved and executed.

If you're still facing issues, examining the specific code sections related to HTTP request handling in Dify's codebase could help identify any potential bugs or areas for improvement.

Details

Sources

• api/core/workflow/nodes/http_request/entities.py
• en/features/workflow/node/http-request.md
• api/core/workflow/nodes/http_request/http_executor.py
• docker/docker-compose.yaml
• zh_CN/getting-started/install-self-hosted/environments.md
• en/getting-started/install-self-hosted/environments.md
• api/.env.example
• web/i18n/de-DE/app-debug.ts
• sdks/nodejs-client/index.test.js
• api/tests/unit_tests/services/workflow/test_workflow_converter.py
• api/tests/integration_tests/workflow/nodes/test_http.py

About Dosu
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

To continue the conversation, mention @dosu.

[AngleMAXIN]

+1

[xiaodong-l]

@dosu. I have deployed two Docker versions of Dify, one on the public network and one on the private network, both experiencing the same issue.

[zeroameli]

@xiaodong-l Check this out #4127, it had been fixed in 0.6.7

[dosubot]

To address the issue with the HTTP request module not saving the POST request settings, including the BODY and API authentication, in Dify version 0.6.6, you should upgrade to Dify version 0.6.7. This version includes fixes specifically for the problems you've encountered. Ensure your Docker deployment uses the updated version by pulling the latest images and restarting your services:

docker-compose pull
docker-compose down
docker-compose up -d

This update should resolve the issue across both public and private network deployments, ensuring that your HTTP request configurations are retained as expected.

Details

Sources

• the http-request node lose json requset data after i saved it
• docker/docker-compose.yaml
• api/tests/integration_tests/workflow/nodes/__mock/http.py
• api/core/workflow/nodes/http_request/http_executor.py
• web/app/components/workflow/nodes/http/types.ts
• zh_CN/getting-started/install-self-hosted/docker-compose.md

About Dosu
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

To continue the conversation, mention @dosu.