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 failure #14863

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

Originally created by @zyjfly on GitHub (Jun 24, 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.4.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image

Image

✔️ Expected Behavior

HTTP request outputs content normally

❌ Actual Behavior

The HTTP request prompt is empty, but I can run the same request normally in Postman

Originally created by @zyjfly on GitHub (Jun 24, 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.4.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce ![Image](https://github.com/user-attachments/assets/c5e97e3e-74c4-4535-81e7-c415901cb96c) ![Image](https://github.com/user-attachments/assets/9e0a868a-b12e-45a1-9f7b-ca12e2360e7e) ### ✔️ Expected Behavior HTTP request outputs content normally ### ❌ Actual Behavior The HTTP request prompt is empty, but I can run the same request normally in Postman
yindo added the 🤔 cant-reproduce label 2026-02-21 19:19:07 -05:00
yindo closed this issue 2026-02-21 19:19:07 -05:00
yindo commented 2026-02-21 19:19:07 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jun 24, 2025):

There are several known issues and limitations with Dify's HTTP request node when handling file uploads and multipart/form-data. Based on similar reports, here are the most relevant troubleshooting steps:

  • Proxy configuration in Docker can block or truncate file uploads. Try increasing the buffer size in your docker/ssrf_proxy/squid.conf.template by adding client_request_buffer_max_size 10240 KB and then re-running the entrypoint script to apply changes. This has resolved similar issues for others [source].
  • Dify enforces file size limits via the HTTP_REQUEST_NODE_MAX_BINARY_SIZE and HTTP_REQUEST_NODE_MAX_TEXT_SIZE environment variables. If your file is large, increase these values in your configuration and restart the services [source].
  • The HTTP request node does not support single file uploads directly; it expects an array of files. If your endpoint requires a single file, use an iteration node or a code node to extract and send the file [source].
  • There is a known limitation where file uploads larger than 800KB may fail. For larger files, use a Python code node as a workaround [source].
  • Double-check that your node configuration sets Content-Type to multipart/form-data and that all required fields (especially the file field) are mapped correctly. Mismatches can result in empty or null inputs [source].
  • If you still see input: null, review your Docker and Dify logs for more detailed error messages.

If you try these steps and the issue persists, let me know what you find in the logs or if you need guidance on setting up a Python code node for file uploads.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

@dosubot[bot] commented on GitHub (Jun 24, 2025): <!-- Answer --> There are several known issues and limitations with Dify's HTTP request node when handling file uploads and multipart/form-data. Based on similar reports, here are the most relevant troubleshooting steps: - Proxy configuration in Docker can block or truncate file uploads. Try increasing the buffer size in your `docker/ssrf_proxy/squid.conf.template` by adding `client_request_buffer_max_size 10240 KB` and then re-running the entrypoint script to apply changes. This has resolved similar issues for others [[source]](https://github.com/langgenius/dify/issues/15008). - Dify enforces file size limits via the `HTTP_REQUEST_NODE_MAX_BINARY_SIZE` and `HTTP_REQUEST_NODE_MAX_TEXT_SIZE` environment variables. If your file is large, increase these values in your configuration and restart the services [[source]](https://github.com/langgenius/dify/issues/15008). - The HTTP request node does not support single file uploads directly; it expects an array of files. If your endpoint requires a single file, use an iteration node or a code node to extract and send the file [[source]](https://github.com/langgenius/dify/issues/14400). - There is a known limitation where file uploads larger than 800KB may fail. For larger files, use a Python code node as a workaround [[source]](https://github.com/langgenius/dify/issues/13634). - Double-check that your node configuration sets `Content-Type` to `multipart/form-data` and that all required fields (especially the file field) are mapped correctly. Mismatches can result in empty or null inputs [[source]](https://github.com/langgenius/dify/issues/13634). - If you still see `input: null`, review your Docker and Dify logs for more detailed error messages. If you try these steps and the issue persists, let me know what you find in the logs or if you need guidance on setting up a Python code node for file uploads. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/723392b6-3bb0-4489-a334-a35d1a09d407?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/723392b6-3bb0-4489-a334-a35d1a09d407?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/723392b6-3bb0-4489-a334-a35d1a09d407?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/723392b6-3bb0-4489-a334-a35d1a09d407?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/723392b6-3bb0-4489-a334-a35d1a09d407?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/723392b6-3bb0-4489-a334-a35d1a09d407?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/723392b6-3bb0-4489-a334-a35d1a09d407?feedback_type=other)</sup>&nbsp;&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/21464)
yindo commented 2026-02-21 19:19:07 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jun 24, 2025):

The images you have provided indicate that you have already make a successful HTTP call, if it fails to invoke HTTP, then it will have error messages not like that. Please check your input again to see if it works.

@crazywoola commented on GitHub (Jun 24, 2025): The images you have provided indicate that you have already make a successful HTTP call, if it fails to invoke HTTP, then it will have error messages not like that. Please check your input again to see if it works.
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 🤔 cant-reproduce
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#14863
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?