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

Missing boundary when using multipart/form-data in HTTP Request component on local Docker deployment #16209

New Issue
Closed
opened 2026-02-21 19:25:05 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 19:25:05 -05:00
Owner
Copy Link
Copy Source

Originally created by @whomata120 on GitHub (Aug 16, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.7.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image

Image

Image

Image

✔️ Expected Behavior

After upgrading from version 1.7.0 to 1.7.2, the previously working form-data is no longer functioning.

❌ Actual Behavior

I pulled the Docker image again, but the issue still persists.

Originally created by @whomata120 on GitHub (Aug 16, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.7.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce ![Image](https://github.com/user-attachments/assets/84f55d24-2399-418c-ae15-3c34aefe4b57) ![Image](https://github.com/user-attachments/assets/2ae3b9f0-9261-49da-95a5-468077df099f) ![Image](https://github.com/user-attachments/assets/04921afb-ef24-4202-bbc1-ef891a14eec2) ![Image](https://github.com/user-attachments/assets/a37b5084-9d75-4235-9563-6940b497e59c) ### ✔️ Expected Behavior After upgrading from version 1.7.0 to 1.7.2, the previously working form-data is no longer functioning. ### ❌ Actual Behavior I pulled the Docker image again, but the issue still persists.
yindo added the 🐞 bug label 2026-02-21 19:25:05 -05:00
yindo closed this issue 2026-02-21 19:25:05 -05:00
yindo commented 2026-02-21 19:25:06 -05:00
Author
Owner
Copy Link
Copy Source

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

Hi @whomata120! I'm Dosu and I’m helping the dify team.

This is a known regression in Dify v1.7.2: the HTTP Request node can emit malformed multipart/form-data bodies with an extra empty part (name=''), causing missing boundary errors and 400 responses from servers like ASP.NET Core. The root cause is a bug in multipart encoding that appeared after the upgrade [source].

This has been fixed in recent updates: two merged pull requests (#23008 and #23903) ensure the HTTP client library (httpx) now handles Content-Type and boundary generation automatically, and filters out empty field names to prevent malformed requests. These fixes are included in the latest codebase after v1.7.2.

To resolve the issue, upgrade your Dify Docker deployment to the latest version. If you can't upgrade right away, you can roll back to v1.7.1, switch to application/json payloads if possible, or avoid empty form fields in your requests [source].

Manual setting of the Content-Type header for multipart/form-data is no longer recommended—let Dify and the HTTP client handle it to ensure the boundary is set correctly [source].

To reply, just mention @dosu.

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

@dosubot[bot] commented on GitHub (Aug 16, 2025): <!-- Greeting --> Hi @whomata120! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> This is a known regression in Dify v1.7.2: the HTTP Request node can emit malformed multipart/form-data bodies with an extra empty part (`name=''`), causing missing boundary errors and 400 responses from servers like ASP.NET Core. The root cause is a bug in multipart encoding that appeared after the upgrade [[source](https://github.com/langgenius/dify/issues/23829)]. This has been fixed in recent updates: two merged pull requests ([#23008](https://github.com/langgenius/dify/pull/23008) and [#23903](https://github.com/langgenius/dify/pull/23903)) ensure the HTTP client library (httpx) now handles Content-Type and boundary generation automatically, and filters out empty field names to prevent malformed requests. These fixes are included in the latest codebase after v1.7.2. To resolve the issue, upgrade your Dify Docker deployment to the latest version. If you can't upgrade right away, you can roll back to v1.7.1, switch to application/json payloads if possible, or avoid empty form fields in your requests [[source](https://github.com/langgenius/dify/issues/23829)]. Manual setting of the Content-Type header for multipart/form-data is no longer recommended—let Dify and the HTTP client handle it to ensure the boundary is set correctly [[source](https://github.com/langgenius/dify/pull/23903)]. <!-- 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/f2c4d046-903f-4988-acc3-678e1da8a6a5?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/f2c4d046-903f-4988-acc3-678e1da8a6a5?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/f2c4d046-903f-4988-acc3-678e1da8a6a5?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/f2c4d046-903f-4988-acc3-678e1da8a6a5?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f2c4d046-903f-4988-acc3-678e1da8a6a5?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/f2c4d046-903f-4988-acc3-678e1da8a6a5?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/f2c4d046-903f-4988-acc3-678e1da8a6a5?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&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/24034)
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#16209
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?