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

File size is too large #5113

New Issue
Closed
opened 2026-02-21 18:09:26 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 18:09:26 -05:00
Owner
Copy Link
Copy Source

Originally created by @CrankGentleman on GitHub (Aug 19, 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.7.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  1. create a chatbot
  2. add llm，line to http tool
  3. http request image url
  4. file size error

1
2

✔️ Expected Behavior

I want to know where this configuration can be changed

❌ Actual Behavior

Run failed: Node HTTP 请求 run failed: File size is too large, max size is 10.00MB, but current size is 24.81 MB.

Originally created by @CrankGentleman on GitHub (Aug 19, 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.7.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 1. create a chatbot 2. add llm，line to http tool 3. http request image url 4. file size error ![1](https://github.com/user-attachments/assets/fa2d8302-91d1-4fc5-9fdb-0f08def3ccfa) ![2](https://github.com/user-attachments/assets/f932a67b-08e5-40c6-ae32-9d0cdb704070) ### ✔️ Expected Behavior I want to know where this configuration can be changed ### ❌ Actual Behavior Run failed: Node HTTP 请求 run failed: File size is too large, max size is 10.00MB, but current size is 24.81 MB.
yindo added the 🐞 bug label 2026-02-21 18:09:26 -05:00
yindo closed this issue 2026-02-21 18:09:27 -05:00
yindo commented 2026-02-21 18:09:27 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 19, 2024):

@CrankGentleman Hello there! I'm here to help you with any bugs, questions, or contributions you may have for the project. Let me know how I can assist you while you wait for a human maintainer.

To change the configuration to allow a larger file size for HTTP requests in Dify version 0.7.1, you need to modify the values of HTTP_REQUEST_NODE_MAX_BINARY_SIZE and HTTP_REQUEST_NODE_MAX_TEXT_SIZE in the .env file.

Here is the relevant part of the .env file where these configurations are used:

# HTTP Node configuration
HTTP_REQUEST_MAX_CONNECT_TIMEOUT=300
HTTP_REQUEST_MAX_READ_TIMEOUT=600
HTTP_REQUEST_MAX_WRITE_TIMEOUT=600
HTTP_REQUEST_NODE_MAX_BINARY_SIZE=10485760 # 10MB
HTTP_REQUEST_NODE_MAX_TEXT_SIZE=1048576 # 1MB

To allow a larger file size, you should update these configuration values in the .env file. For example:

# HTTP Node configuration
HTTP_REQUEST_MAX_CONNECT_TIMEOUT=300
HTTP_REQUEST_MAX_READ_TIMEOUT=600
HTTP_REQUEST_MAX_WRITE_TIMEOUT=600
HTTP_REQUEST_NODE_MAX_BINARY_SIZE=26214400 # 25MB
HTTP_REQUEST_NODE_MAX_TEXT_SIZE=26214400 # 25MB

Adjust the values as needed to fit your requirements [1].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Aug 19, 2024): <!-- Greeting --> @CrankGentleman Hello there! I'm here to help you with any bugs, questions, or contributions you may have for the project. Let me know how I can assist you while you wait for a human maintainer. <!-- Answer --> To change the configuration to allow a larger file size for HTTP requests in Dify version 0.7.1, you need to modify the values of `HTTP_REQUEST_NODE_MAX_BINARY_SIZE` and `HTTP_REQUEST_NODE_MAX_TEXT_SIZE` in the `.env` file. Here is the relevant part of the `.env` file where these configurations are used: ```env # HTTP Node configuration HTTP_REQUEST_MAX_CONNECT_TIMEOUT=300 HTTP_REQUEST_MAX_READ_TIMEOUT=600 HTTP_REQUEST_MAX_WRITE_TIMEOUT=600 HTTP_REQUEST_NODE_MAX_BINARY_SIZE=10485760 # 10MB HTTP_REQUEST_NODE_MAX_TEXT_SIZE=1048576 # 1MB ``` To allow a larger file size, you should update these configuration values in the `.env` file. For example: ```env # HTTP Node configuration HTTP_REQUEST_MAX_CONNECT_TIMEOUT=300 HTTP_REQUEST_MAX_READ_TIMEOUT=600 HTTP_REQUEST_MAX_WRITE_TIMEOUT=600 HTTP_REQUEST_NODE_MAX_BINARY_SIZE=26214400 # 25MB HTTP_REQUEST_NODE_MAX_TEXT_SIZE=26214400 # 25MB ``` Adjust the values as needed to fit your requirements <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/.env.example)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:09:27 -05:00
Author
Owner
Copy Link
Copy Source

@fuwj1994 commented on GitHub (Dec 19, 2025):

@CrankGentleman Hello there! I'm here to help you with any bugs, questions, or contributions you may have for the project. Let me know how I can assist you while you wait for a human maintainer.

To change the configuration to allow a larger file size for HTTP requests in Dify version 0.7.1, you need to modify the values of HTTP_REQUEST_NODE_MAX_BINARY_SIZE and HTTP_REQUEST_NODE_MAX_TEXT_SIZE in the .env file.

Here is the relevant part of the .env file where these configurations are used:

HTTP Node configuration

HTTP_REQUEST_MAX_CONNECT_TIMEOUT=300
HTTP_REQUEST_MAX_READ_TIMEOUT=600
HTTP_REQUEST_MAX_WRITE_TIMEOUT=600
HTTP_REQUEST_NODE_MAX_BINARY_SIZE=10485760 # 10MB
HTTP_REQUEST_NODE_MAX_TEXT_SIZE=1048576 # 1MB
To allow a larger file size, you should update these configuration values in the .env file. For example:

HTTP Node configuration

HTTP_REQUEST_MAX_CONNECT_TIMEOUT=300
HTTP_REQUEST_MAX_READ_TIMEOUT=600
HTTP_REQUEST_MAX_WRITE_TIMEOUT=600
HTTP_REQUEST_NODE_MAX_BINARY_SIZE=26214400 # 25MB
HTTP_REQUEST_NODE_MAX_TEXT_SIZE=26214400 # 25MB
Adjust the values as needed to fit your requirements [1].

To continue talking to Dosu, mention @dosu.

okkkkkk!!

please remember modify the .env file

@fuwj1994 commented on GitHub (Dec 19, 2025): > [@CrankGentleman](https://github.com/CrankGentleman) Hello there! I'm here to help you with any bugs, questions, or contributions you may have for the project. Let me know how I can assist you while you wait for a human maintainer. > > To change the configuration to allow a larger file size for HTTP requests in Dify version 0.7.1, you need to modify the values of `HTTP_REQUEST_NODE_MAX_BINARY_SIZE` and `HTTP_REQUEST_NODE_MAX_TEXT_SIZE` in the `.env` file. > > Here is the relevant part of the `.env` file where these configurations are used: > > # HTTP Node configuration > HTTP_REQUEST_MAX_CONNECT_TIMEOUT=300 > HTTP_REQUEST_MAX_READ_TIMEOUT=600 > HTTP_REQUEST_MAX_WRITE_TIMEOUT=600 > HTTP_REQUEST_NODE_MAX_BINARY_SIZE=10485760 # 10MB > HTTP_REQUEST_NODE_MAX_TEXT_SIZE=1048576 # 1MB > To allow a larger file size, you should update these configuration values in the `.env` file. For example: > > # HTTP Node configuration > HTTP_REQUEST_MAX_CONNECT_TIMEOUT=300 > HTTP_REQUEST_MAX_READ_TIMEOUT=600 > HTTP_REQUEST_MAX_WRITE_TIMEOUT=600 > HTTP_REQUEST_NODE_MAX_BINARY_SIZE=26214400 # 25MB > HTTP_REQUEST_NODE_MAX_TEXT_SIZE=26214400 # 25MB > Adjust the values as needed to fit your requirements [[1]](https://github.com/langgenius/dify/blob/main/api/.env.example). > > _To continue talking to [Dosu](https://dosu.dev), mention [@dosu](https://github.com/dosu)._ okkkkkk!! please remember modify the .env file
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#5113
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?