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

Umlauts cause 400 error in POST /segments API call #12540

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

Originally created by @Nausoj on GitHub (Apr 4, 2025).

Originally assigned to: @crazywoola on GitHub.

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

v1.1.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

end a POST request to the following endpoint:
POST /datasets/{dataset_id}/documents/{document_id}/segments

Include content with German umlauts like "Beispiel mit Äpfeln und Öfen"

Observe that the server responds with HTTP 400

Example Request (cURL):
curl --location --request POST 'http://your-dify-instance.local/v1/datasets/{dataset_id}/documents/{document_id}/segments'
--header 'Authorization: Bearer {api_key}'
--header 'Content-Type: application/json'
--data-raw '{
"segments": [
{
"content": "Beispiel mit Äpfeln und Öfen",
"answer": "Dies ist eine Antwort",
"keywords": ["Beispiel", "Umlaute"]
}
]
}'

Response:
{
"code": "bad_request",
"message": "The browser (or proxy) sent a request that this server could not understand.",
"status": 400
}

✔️ Expected Behavior

The segment should be added successfully even if the content contains umlauts.

❌ Actual Behavior

The request fails with HTTP 400. The error message suggests the server is unable to parse the request correctly.

Originally created by @Nausoj on GitHub (Apr 4, 2025). Originally assigned to: @crazywoola on GitHub. ### 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 v1.1.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce end a POST request to the following endpoint: POST /datasets/{dataset_id}/documents/{document_id}/segments Include content with German umlauts like "Beispiel mit Äpfeln und Öfen" Observe that the server responds with HTTP 400 Example Request (cURL): curl --location --request POST 'http://your-dify-instance.local/v1/datasets/{dataset_id}/documents/{document_id}/segments' \ --header 'Authorization: Bearer {api_key}' \ --header 'Content-Type: application/json' \ --data-raw '{ "segments": [ { "content": "Beispiel mit Äpfeln und Öfen", "answer": "Dies ist eine Antwort", "keywords": ["Beispiel", "Umlaute"] } ] }' Response: { "code": "bad_request", "message": "The browser (or proxy) sent a request that this server could not understand.", "status": 400 } ### ✔️ Expected Behavior The segment should be added successfully even if the content contains umlauts. ### ❌ Actual Behavior The request fails with HTTP 400. The error message suggests the server is unable to parse the request correctly.
yindo added the 🐞 bugstale labels 2026-02-21 19:07:53 -05:00
yindo closed this issue 2026-02-21 19:07:53 -05:00
yindo commented 2026-02-21 19:07:53 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (May 5, 2025):

Hi, @Nausoj. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.

Issue Summary:

  • You reported a bug in the POST /segments API call on a self-hosted Dify version 1.1.3 using Docker.
  • Requests containing German umlauts result in a 400 error.
  • The server fails to process these requests, which should be handled successfully.
  • No comments or developments have been made on this issue yet.

Next Steps:

  • Please let me know if this issue is still relevant to the latest version of the Dify repository by commenting here.
  • If there is no further activity, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (May 5, 2025): Hi, @Nausoj. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog. I'm marking this issue as stale. **Issue Summary:** - You reported a bug in the POST /segments API call on a self-hosted Dify version 1.1.3 using Docker. - Requests containing German umlauts result in a 400 error. - The server fails to process these requests, which should be handled successfully. - No comments or developments have been made on this issue yet. **Next Steps:** - Please let me know if this issue is still relevant to the latest version of the Dify repository by commenting here. - If there is no further activity, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
yindo commented 2026-02-21 19:07:54 -05:00
Author
Owner
Copy Link
Copy Source

@Nausoj commented on GitHub (May 6, 2025):

Hello Dosu,The problem is still present in the latest version 1.3.1.Thank you and best regardsJosuan Mc Clellan On 5. May 2025, at 18:01, dosubot[bot] @.***> wrote:
dosubot[bot] left a comment (langgenius/dify#17446)
Hi, @Nausoj. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.
Issue Summary:

You reported a bug in the POST /segments API call on a self-hosted Dify version 1.1.3 using Docker.
Requests containing German umlauts result in a 400 error.
The server fails to process these requests, which should be handled successfully.
No comments or developments have been made on this issue yet.

Next Steps:

Please let me know if this issue is still relevant to the latest version of the Dify repository by commenting here.
If there is no further activity, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

@Nausoj commented on GitHub (May 6, 2025): Hello Dosu,The problem is still present in the latest version 1.3.1.Thank you and best regardsJosuan Mc Clellan On 5. May 2025, at 18:01, dosubot[bot] ***@***.***> wrote: dosubot[bot] left a comment (langgenius/dify#17446) Hi, @Nausoj. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale. Issue Summary: You reported a bug in the POST /segments API call on a self-hosted Dify version 1.1.3 using Docker. Requests containing German umlauts result in a 400 error. The server fails to process these requests, which should be handled successfully. No comments or developments have been made on this issue yet. Next Steps: Please let me know if this issue is still relevant to the latest version of the Dify repository by commenting here. If there is no further activity, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution! —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
yindo commented 2026-02-21 19:07:54 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (May 6, 2025):

@crazywoola, the user @Nausoj has confirmed that the issue with the POST /segments API call is still present in the latest version 1.3.1. Could you please assist them with this bug?

@dosubot[bot] commented on GitHub (May 6, 2025): @crazywoola, the user @Nausoj has confirmed that the issue with the POST /segments API call is still present in the latest version 1.3.1. Could you please assist them with this bug?
yindo commented 2026-02-21 19:07:54 -05:00
Author
Owner
Copy Link
Copy Source

@Nausoj commented on GitHub (May 8, 2025):

Wie soll ich mir bei diesem Fehler selbst helfen? Bitte informiere das Team noch mal das der Fehler in der aktuellen Version besteht. On 6. May 2025, at 18:10, dosubot[bot] @.***> wrote:
dosubot[bot] left a comment (langgenius/dify#17446)
@crazywoola, the user @Nausoj has confirmed that the issue with the POST /segments API call is still present in the latest version 1.3.1. Could you please assist them with this bug?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

@Nausoj commented on GitHub (May 8, 2025): Wie soll ich mir bei diesem Fehler selbst helfen? Bitte informiere das Team noch mal das der Fehler in der aktuellen Version besteht. On 6. May 2025, at 18:10, dosubot[bot] ***@***.***> wrote: dosubot[bot] left a comment (langgenius/dify#17446) @crazywoola, the user @Nausoj has confirmed that the issue with the POST /segments API call is still present in the latest version 1.3.1. Could you please assist them with this bug? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
yindo commented 2026-02-21 19:07:54 -05:00
Author
Owner
Copy Link
Copy Source

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

Hi, @Nausoj. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported that POST requests with German umlauts to the /segments API endpoint cause a 400 Bad Request error on self-hosted Dify.
  • The issue was first observed in version 1.1.3 and confirmed to persist in version 1.3.1.
  • The problem has been acknowledged but remains unresolved.
  • Maintainer @crazywoola has been requested to assist with this bug.
  • You are seeking guidance on resolving the issue and want the team to acknowledge the ongoing problem.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open.
  • If I do not hear back within 15 days, I will automatically close this issue.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Aug 24, 2025): Hi, @Nausoj. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported that POST requests with German umlauts to the /segments API endpoint cause a 400 Bad Request error on self-hosted Dify. - The issue was first observed in version 1.1.3 and confirmed to persist in version 1.3.1. - The problem has been acknowledged but remains unresolved. - Maintainer @crazywoola has been requested to assist with this bug. - You are seeking guidance on resolving the issue and want the team to acknowledge the ongoing problem. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open. - If I do not hear back within 15 days, I will automatically close this issue. Thank you for your understanding and contribution!
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 stale 🐞 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#12540
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?