langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-22 12:36:14 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Http executor node not uploading files to another server #6418

New Issue
Closed
opened 2026-02-21 18:15:39 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 18:15:39 -05:00
Owner
Copy Link
Copy Source

Originally created by @je4ngomes on GitHub (Oct 29, 2024).

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

0.10.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  • Create a workflow where the user can send files
  • Add a Http Executor node
  • Try to upload a file through http node

✔️ Expected Behavior

Be able to access the uploaded file on the server side

❌ Actual Behavior

The http node is not uploading the actual file

Originally created by @je4ngomes on GitHub (Oct 29, 2024). ### 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 0.10.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce - Create a workflow where the user can send files - Add a Http Executor node - Try to upload a file through http node ### ✔️ Expected Behavior Be able to access the uploaded file on the server side ### ❌ Actual Behavior The http node is not uploading the actual file
yindo added the 🐞 bug label 2026-02-21 18:15:39 -05:00
yindo closed this issue 2026-02-21 18:15:39 -05:00
yindo commented 2026-02-21 18:15:40 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 29, 2024):

Hey @je4ngomes! I'm here to help you with any bugs, questions, or contributions you have in mind. Let's work together to solve this issue.

I couldn't find a specific solution for the Http Executor node not uploading files in Dify version 0.10.1. However, I can provide some insights into how the Http Executor node handles file uploads and some common configuration issues that might affect this functionality.

The Http Executor node in Dify uses the HTTP protocol to interact with external servers and supports various HTTP methods, including "post" and "put" for file uploads. It uses the "multipart/form-data" content type for file uploads, which is specified in the headers when the body type is "form-data". The files are prepared as a dictionary where each file is represented as a tuple containing the filename, file content, and MIME type. The request is executed using the httpx library, which handles the HTTP communication with the external server [1].

If you're experiencing issues with file uploads, ensure that the following configurations are correctly set:

  1. FILES_URL: This should be set to an externally accessible address so that the server can access the file. The URL must include a signature with a 5-minute expiration to prevent forgery.
  2. STORAGE_TYPE: Ensure that the storage type is correctly set to either local, s3, or azure-blob based on your storage setup.

For example, if you are using local storage, you need to set:

STORAGE_TYPE=local
STORAGE_LOCAL_PATH=/path/to/storage
FILES_URL=http://your-domain.com/path/to/storage

If you are using S3, you need to set:

STORAGE_TYPE=s3
S3_ENDPOINT=your-s3-endpoint
S3_BUCKET_NAME=your-bucket-name
S3_ACCESS_KEY=your-access-key
S3_SECRET_KEY=your-secret-key
FILES_URL=https://your-s3-endpoint/your-bucket-name

Ensure these configurations are correctly set in your environment variables to enable file upload functionalities [2].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Oct 29, 2024): <!-- Greeting --> Hey @je4ngomes! I'm here to help you with any bugs, questions, or contributions you have in mind. Let's work together to solve this issue. <!-- Answer --> I couldn't find a specific solution for the Http Executor node not uploading files in Dify version 0.10.1. However, I can provide some insights into how the Http Executor node handles file uploads and some common configuration issues that might affect this functionality. The Http Executor node in Dify uses the HTTP protocol to interact with external servers and supports various HTTP methods, including "post" and "put" for file uploads. It uses the "multipart/form-data" content type for file uploads, which is specified in the headers when the body type is "form-data". The files are prepared as a dictionary where each file is represented as a tuple containing the filename, file content, and MIME type. The request is executed using the `httpx` library, which handles the HTTP communication with the external server <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/core/workflow/nodes/http_request/executor.py)</sup>. If you're experiencing issues with file uploads, ensure that the following configurations are correctly set: 1. **FILES_URL**: This should be set to an externally accessible address so that the server can access the file. The URL must include a signature with a 5-minute expiration to prevent forgery. 2. **STORAGE_TYPE**: Ensure that the storage type is correctly set to either `local`, `s3`, or `azure-blob` based on your storage setup. For example, if you are using local storage, you need to set: ```env STORAGE_TYPE=local STORAGE_LOCAL_PATH=/path/to/storage FILES_URL=http://your-domain.com/path/to/storage ``` If you are using S3, you need to set: ```env STORAGE_TYPE=s3 S3_ENDPOINT=your-s3-endpoint S3_BUCKET_NAME=your-bucket-name S3_ACCESS_KEY=your-access-key S3_SECRET_KEY=your-secret-key FILES_URL=https://your-s3-endpoint/your-bucket-name ``` Ensure these configurations are correctly set in your environment variables to enable file upload functionalities <sup>[[2]](https://github.com/langgenius/dify/discussions/9748)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:15:40 -05:00
Author
Owner
Copy Link
Copy Source

@je4ngomes commented on GitHub (Oct 29, 2024):

The problem is not related to uploading files into dify, but transferring the actual file to another server using the http executor inside a workflow.

Here is a exemple of the request being received on n8n from dify workflow, as you will see no binary file:
image
image

Now here is what should be an expected behavior (This one is from postman now):
image
image

@je4ngomes commented on GitHub (Oct 29, 2024): The problem is not related to uploading files into dify, but transferring the actual file to another server using the http executor inside a workflow. Here is a exemple of the request being received on n8n from dify workflow, as you will see no binary file: ![image](https://github.com/user-attachments/assets/3df69b2a-416a-417b-931c-59b1daffb710) ![image](https://github.com/user-attachments/assets/82bf6b6e-ae6d-46ea-8f6a-8d528b5a5516) Now here is what should be an expected behavior (This one is from postman now): ![image](https://github.com/user-attachments/assets/4eb5f2bd-051c-4f80-a46f-ff1d6ccf7a08) ![image](https://github.com/user-attachments/assets/2fcf7306-1aa8-4e52-8f95-2441a6612c7f)
yindo commented 2026-02-21 18:15:40 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 29, 2024):

Hi, @je4ngomes. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.

Issue Summary

  • Bug in the Http Executor node of Dify version 0.10.2.
  • Files are not being transferred to another server as expected.
  • You clarified the issue is with file transfer within a workflow, not file uploads to Dify.
  • Examples show missing binary files in requests received by n8n, unlike Postman.

Next Steps

  • Is this issue still relevant to the latest version of the Dify repository? If so, please comment to keep the discussion open.
  • Otherwise, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Nov 29, 2024): Hi, @je4ngomes. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog. I'm marking this issue as stale. **Issue Summary** - Bug in the Http Executor node of Dify version 0.10.2. - Files are not being transferred to another server as expected. - You clarified the issue is with file transfer within a workflow, not file uploads to Dify. - Examples show missing binary files in requests received by n8n, unlike Postman. **Next Steps** - Is this issue still relevant to the latest version of the Dify repository? If so, please comment to keep the discussion open. - Otherwise, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
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#6418
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?