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

use dify datasets api in workflow http requests 444 #5316

New Issue
Closed
opened 2026-02-21 18:10:23 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 18:10:23 -05:00
Owner
Copy Link
Copy Source

Originally created by @silverWolf818 on GitHub (Aug 30, 2024).

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

0.7.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

image http return 444 why

same use curl --location --request POST 'http://dify.xxxx/v1/datasets'
--header 'Authorization: Bearer {api_key}'
--header 'Content-Type: application/json'
--data-raw '{"name": "name"}'
can work well

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @silverWolf818 on GitHub (Aug 30, 2024). ### 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 0.7.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce <img width="2303" alt="image" src="https://github.com/user-attachments/assets/1729cff2-d872-4f32-9e09-0a7a37374704"> http return 444 why same use curl --location --request POST 'http://dify.xxxx/v1/datasets' \ --header 'Authorization: Bearer {api_key}' \ --header 'Content-Type: application/json' \ --data-raw '{"name": "name"}' can work well ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug🤔 cant-reproduce labels 2026-02-21 18:10:23 -05:00
yindo closed this issue 2026-02-21 18:10:23 -05:00
yindo commented 2026-02-21 18:10:23 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 30, 2024):

@silverWolf818 Hello there! I'm here to help you with any bugs, questions, or contributions. I'll assist you while we wait for a human maintainer.

The HTTP request to the Dify datasets API returns a 444 status code in the workflow because the API token used in the workflow might not be correctly set or authorized. Ensure that the API token is correctly included in the workflow request headers, similar to how it is done in the curl examples:

--header 'Authorization: Bearer {api_key}'

If the token is missing or incorrect, the server might return a 444 status code, indicating that the request was closed without processing. Additionally, make sure that the API token has the necessary permissions to access the datasets API [1][2][3][4].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Aug 30, 2024): <!-- Greeting --> @silverWolf818 Hello there! I'm here to help you with any bugs, questions, or contributions. I'll assist you while we wait for a human maintainer. <!-- Answer --> The HTTP request to the Dify datasets API returns a 444 status code in the workflow because the API token used in the workflow might not be correctly set or authorized. Ensure that the API token is correctly included in the workflow request headers, similar to how it is done in the curl examples: ```bash --header 'Authorization: Bearer {api_key}' ``` If the token is missing or incorrect, the server might return a 444 status code, indicating that the request was closed without processing. Additionally, make sure that the API token has the necessary permissions to access the datasets API <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/guides/knowledge-base/maintain-dataset-via-api.md)</sup><sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/jp/guides/knowledge-base/maintain-dataset-via-api.md)</sup><sup>[[3]](https://github.com/langgenius/dify-docs/blob/main/jp/features/datasets/maintain-dataset-via-api.md)</sup><sup>[[4]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/features/datasets/maintain-dataset-via-api.md)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:10:23 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Aug 30, 2024):

I don't think this is return by our application, I guess there is something wrong with the request itself or the nginx configuration file is not correct.

QQ_1725013174948

@crazywoola commented on GitHub (Aug 30, 2024): I don't think this is return by our application, I guess there is something wrong with the request itself or the nginx configuration file is not correct. ![QQ_1725013174948](https://github.com/user-attachments/assets/7d3a04a3-ea6b-4c1d-abab-146e392d8060)
yindo commented 2026-02-21 18:10:23 -05:00
Author
Owner
Copy Link
Copy Source

@silverWolf818 commented on GitHub (Aug 30, 2024):

ok , try it

@silverWolf818 commented on GitHub (Aug 30, 2024): ok , try it
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 🤔 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#5316
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?