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 workflow API lacks validation for file upload methods #11229

New Issue
Closed
opened 2026-02-21 18:57:12 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 18:57:12 -05:00
Owner
Copy Link
Copy Source

Originally created by @lrhan321 on GitHub (Mar 16, 2025).

Self Checks

  • This is only for bug report, if you would like to ask a question, 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).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.0.1

Cloud or Self Hosted

Self Hosted (Docker), Self Hosted (Source)

Steps to reproduce

  1. Create a workflow, add a file variable at the start node, specify the upload method as local, and then publish the workflow.
  2. Create an API key, and request the workflow through the API, specifying the transfer_method of the file as remote_url, and provide a valid url.

Image

✔️ Expected Behavior

The workflow API should not run properly because the upload method was specified as "local" during orchestration.

❌ Actual Behavior

The workflow can run successfully, which is inconsistent with the behavior defined by the orchestration. Additionally, this may lead to unforeseen issues later on.

Image

Originally created by @lrhan321 on GitHub (Mar 16, 2025). ### Self Checks - [x] This is only for bug report, if you would like to ask a question, 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] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.0.1 ### Cloud or Self Hosted Self Hosted (Docker), Self Hosted (Source) ### Steps to reproduce 1. Create a workflow, add a file variable at the start node, specify the upload method as local, and then publish the workflow. 2. Create an API key, and request the workflow through the API, specifying the `transfer_method` of the file as `remote_url`, and provide a valid `url`. ![Image](https://github.com/user-attachments/assets/a6074d76-921c-42dc-8661-ed2453b60586) ### ✔️ Expected Behavior The workflow API should not run properly because the upload method was specified as "local" during orchestration. ### ❌ Actual Behavior The workflow can run successfully, which is inconsistent with the behavior defined by the orchestration. Additionally, this may lead to unforeseen issues later on. ![Image](https://github.com/user-attachments/assets/0abc7858-266f-46ad-91e2-e142b3f43b7a)
yindo added the 🐞 bug label 2026-02-21 18:57:12 -05:00
yindo closed this issue 2026-02-21 18:57:12 -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#11229
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?