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

The problem that the setting of the maximum timeout limit for the HTTP component fails to take effect #11536

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

Originally created by @cloudy-Meng on GitHub (Mar 18, 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)

Steps to reproduce

The current maximum timeout limit in the HTTP component is 600 seconds, and I hope to increase the upper limit of this timeout duration.
I tried to increase the values of the three parameters, namely HTTP_REQUEST_MAX_CONNECT_TIMEOUT, HTTP_REQUEST_MAX_READ_TIMEOUT, and HTTP_REQUEST_MAX_WRITE_TIMEOUT, in the.env file of the api/work application to 3000. After making the modifications, I restarted the application. However, I found that the changes did not take effect. In the page, the maximum value that can still be set for the timeout is still 600.

Image

✔️ Expected Behavior

May I ask how to solve this problem?
How can I effectively modify the maximum timeout event of the HTTP component and correctly set it on the page?

❌ Actual Behavior

No response

Originally created by @cloudy-Meng on GitHub (Mar 18, 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) ### Steps to reproduce The current maximum timeout limit in the HTTP component is 600 seconds, and I hope to increase the upper limit of this timeout duration. I tried to increase the values of the three parameters, namely HTTP_REQUEST_MAX_CONNECT_TIMEOUT, HTTP_REQUEST_MAX_READ_TIMEOUT, and HTTP_REQUEST_MAX_WRITE_TIMEOUT, in the.env file of the api/work application to 3000. After making the modifications, I restarted the application. However, I found that the changes did not take effect. In the page, the maximum value that can still be set for the timeout is still 600. <img width="512" alt="Image" src="https://github.com/user-attachments/assets/8b6c9bc3-a71b-4dd7-9c68-49e9156f4a35" /> ### ✔️ Expected Behavior May I ask how to solve this problem? How can I effectively modify the maximum timeout event of the HTTP component and correctly set it on the page? ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 19:00:54 -05:00
yindo closed this issue 2026-02-21 19:00:54 -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#11536
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?