File upload related functions cannot be implemented by adding http request nodes.

langgenius / dify

Dify is an open-source LLM app development platform. Dify's intuitive interface combines AI workflow, RAG pipeline, agent capabilities, model management, observability features and more, letting you quickly go from prototype to production.

Other

51.51k stars 7.44k forks source link

Self Checks

[X] This is only for bug report, if you would like to ask a question, please head to Discussions.
[X] I have searched for existing issues search for existing issues, including closed ones.
[X] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
[X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
[X] Please do not modify this template :) and fill in all the required fields.

Dify version

0.10.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

The content of the document can be read by adding the node of the document extractor, but some documents, such as word, contain tables. Such documents cannot be processed by adding the node of the document extractor, so I want to add the node of the http request. deal with. But I am using node config for http request and I am not able to achieve

This is the interface I wrote： curl -X 'POST' \ 'http://172.17.60.18:18207/file_parse/' \ -H 'accept: application/json' \ -H 'Content-Type: multipart/form-data' \ -F 'files=@测试.txt;type=text/plain'

This is the http request node I configured

This is done by adding http request node background log as follows, where does this "upload" come from?

This is the log directly called through curl

✔️ Expected Behavior

I hope to extract complex document content by configuring the http request node to call the interface I wrote to add the attachment function.

❌ Actual Behavior

Configuring the http request interface cannot implement the document upload and parsing function

To address the issue of file uploads not working as expected with the HTTP request node in Dify, there are a few things to consider:

File Naming Discrepancy: The discrepancy in file names between your curl command and the HTTP request node might be due to how the filename is being set in the HTTP request node. In Dify, the filename is typically derived from the URL's basename or guessed from the content type. If the filename is appearing as "upload" in the HTTP request node, it might be due to the way the file path or name is being specified in the node configuration ^[1].
Configuration of HTTP Request Node: Ensure that the HTTP request node is correctly configured to handle multipart form-data. The Content-Type should be set to multipart/form-data, and the file should be included in the form-data with the correct key. The BodyData object should have its type set to "file" and the file attribute should point to the correct file path or identifier ^[2].
Boundary and Headers: The Executor class in Dify handles multipart form-data by setting the Content-Type header with a boundary. Ensure that this is correctly set in your configuration. The boundary is crucial for separating parts of the form data ^[3].
File Upload Handling: If the HTTP request node is not handling the file upload as expected, double-check the file path and ensure that the file is accessible and correctly specified in the node configuration. Also, verify that the server endpoint is correctly set up to receive multipart form-data and process the file accordingly.

By ensuring these configurations are correct, you should be able to achieve the desired file upload and parsing functionality using the HTTP request node in Dify.

To continue talking to Dosu, mention @dosu.

langgenius / dify