#22880Missing boundary when using multipart/form-data in HTTP Request component on Dify public cloud

dify
dify
langgenius

Production-ready platform for agentic workflow development.

Issue Details

5 months ago
No assignee
🐞 buggood first issue🌊 feat:workflow
View on GitHub
QuanXplorQuanXplor
opened 5 months ago
Author

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

Cloud or Self Hosted

Cloud

Steps to reproduce

  1. Create a new workflow in Dify public cloud
  2. In the Start component, add a file upload field (to receive the file input)
Image

  1. Add an HTTP Request component to the workflow

  2. Configure the HTTP Request component to use POST method

  3. Set Body to form-data

Image
  1. Map the file from the Start component's upload field to the HTTP Request's file parameters
Image
  1. Execute the workflow
Image

✔️ Expected Behavior

The HTTP Request should properly format the multipart/form-data request with a valid boundary in the Content-Type header (e.g., multipart/form-data; boundary=--------------------------749422656485593958486831), allowing successful file uploads.

Image

❌ Actual Behavior

While the request header includes Content-Type: multipart/form-data; boundary=----[random string], the actual request body does not contain the specified boundary strings to separate the content parts. This mismatch causes the server to reject the request with an error about invalid multipart formatting.

Image