langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 20:15:31 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

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

New Issue
Closed
opened 2026-02-21 17:52:33 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 17:52:33 -05:00
Owner
Copy Link
Copy Source

Originally created by @xiaodong-l on GitHub (May 7, 2024).

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

Originally created by @xiaodong-l on GitHub (May 7, 2024). ### Self Checks - [X] This is only for bug report, if you would like to ask a quesion, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] 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_
yindo added the 🐞 bug label 2026-02-21 17:52:33 -05:00
yindo closed this issue 2026-02-21 17:52:33 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#2999
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?