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

http-request node support response event-stream #14049

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

Originally created by @erikwoo on GitHub (May 20, 2025).

Self Checks

  • 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.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

I'm trying to use http-request node to fetch stream data from other api server for parsing image, acting like other llm server. The api server would response with event-stream,

 return Response(
        stream_with_context(chat_sse(request_data, SSEUrl)),
        content_type="text/event-stream"
    )

but the http-request node would wait for the end.

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @erikwoo on GitHub (May 20, 2025). ### Self Checks - [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. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. I'm trying to use http-request node to fetch stream data from other api server for parsing image, acting like other llm server. The api server would response with event-stream, ```py return Response( stream_with_context(chat_sse(request_data, SSEUrl)), content_type="text/event-stream" ) ``` but the http-request node would wait for the end. ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [x] I am interested in contributing to this feature.
yindo added the 🔨 feat:tools label 2026-02-21 19:15:18 -05:00
yindo closed this issue 2026-02-21 19:15:18 -05:00
yindo commented 2026-02-21 19:15:18 -05:00
Author
Owner
Copy Link
Copy Source

@gaoconggit commented on GitHub (May 27, 2025):

I have the same problem

@gaoconggit commented on GitHub (May 27, 2025): I have the same problem
yindo commented 2026-02-21 19:15:18 -05:00
Author
Owner
Copy Link
Copy Source

@sillsun commented on GitHub (Jun 8, 2025):

I have the same problem, dose the http-request node support streaming content?

@sillsun commented on GitHub (Jun 8, 2025): I have the same problem, dose the http-request node support streaming content?
yindo commented 2026-02-21 19:15:18 -05:00
Author
Owner
Copy Link
Copy Source

@saneast commented on GitHub (Jun 9, 2025):

same problem

@saneast commented on GitHub (Jun 9, 2025): same problem
yindo commented 2026-02-21 19:15:18 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 31, 2025):

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

Issue Summary:

  • You requested support for handling event-stream (SSE) responses in the http-request node to enable incremental processing of streaming data.
  • Multiple users including gaoconggit, sillsun, and saneast have expressed similar interest, indicating community demand.
  • You have also shown willingness to contribute to implementing this feature.
  • The issue remains unresolved with no recent updates or progress.

Next Steps:

  • Please let me know if this issue is still relevant to the latest version of Dify by commenting here 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 (Aug 31, 2025): Hi, @erikwoo. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You requested support for handling event-stream (SSE) responses in the http-request node to enable incremental processing of streaming data. - Multiple users including gaoconggit, sillsun, and saneast have expressed similar interest, indicating community demand. - You have also shown willingness to contribute to implementing this feature. - The issue remains unresolved with no recent updates or progress. **Next Steps:** - Please let me know if this issue is still relevant to the latest version of Dify by commenting here to keep the discussion open. - Otherwise, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
yindo commented 2026-02-21 19:15:18 -05:00
Author
Owner
Copy Link
Copy Source

@silvery2012 commented on GitHub (Aug 31, 2025):

您好，何威盛已收到您的邮件。

@silvery2012 commented on GitHub (Aug 31, 2025): 您好，何威盛已收到您的邮件。
yindo commented 2026-02-21 19:15:19 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 31, 2025):

@crazywoola The user silvery2012 has confirmed the issue is still relevant and mentioned they have received your email. Could you please assist them with the event-stream (SSE) support in the http-request node?

@dosubot[bot] commented on GitHub (Aug 31, 2025): @crazywoola The user silvery2012 has confirmed the issue is still relevant and mentioned they have received your email. Could you please assist them with the event-stream (SSE) support in the http-request node?
yindo commented 2026-02-21 19:15:19 -05:00
Author
Owner
Copy Link
Copy Source

@silvery2012 commented on GitHub (Oct 16, 2025):

您好，何威盛已收到您的邮件。

@silvery2012 commented on GitHub (Oct 16, 2025): 您好，何威盛已收到您的邮件。
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 🔨 feat:tools
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#14049
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?