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

HTTP request block returns empty body when requesting RSS feed #9654

New Issue
Closed
opened 2026-02-21 18:37:22 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 18:37:22 -05:00
Owner
Copy Link
Copy Source

Originally created by @hirofratica on GitHub (Mar 6, 2025).

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

1.0.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

In the latest version of Dify, the “HTTP request” block returns an empty body when making a GET request to an RSS feed URL.
This issue was not present in version 0.15.3, where the body contained the expected RSS feed content.

  1. Use the “HTTP request” block in a Dify workflow.
  2. Set the method to GET.
  3. Use the following RSS feed URL as the request URL example : https://www.soumu.go.jp/news.rdf

Additional Information
• This issue occurs consistently when requesting RSS feeds.
• It was working correctly in version 0.15.3.
• The headers confirm that the response contains data (content-length: 13362), but the body is empty.
• The content appears to be stored as a file instead, which is not the expected behavior.

✔️ Expected Behavior

The response body should contain the RSS feed content, as it did in version 0.15.3.

❌ Actual Behavior

{
"status_code": 200,
"body": "",
"headers": {
"content-type": "text/xml",
"content-length": "13362",
"connection": "keep-alive",
"server": "Apache",
"date": "Fri, 07 Mar 2025 01:49:25 GMT",
"x-xss-protection": "1; mode=block",
"accept-ranges": "bytes",
"x-content-type-options": "nosniff",
"etag": ""3432-62fb62e8cf08d"",
"last-modified": "Fri, 07 Mar 2025 01:02:51 GMT",
"x-frame-options": "deny",
"x-iij-cache": "HIT"
},
"files": [
{
"dify_model_identity": "dify__file",
"id": null,
"tenant_id": "69f34d1a-7fcf-4528-b693-65b1e388e362",
"type": "document",
"transfer_method": "tool_file",
"remote_url": null,
"related_id": "8ef3d7e5-9568-45a0-9173-042dccd40b8b",
"filename": "xxxxxxxxxx.xml",
"extension": ".xml",
"mime_type": "text/xml",
"size": 13362,
"url": "/files/tools/8ef3d7e5-9568-45a0-9173-xxxxxxxxx.xml?timestamp=1741312286&nonce=XXXXXXXXXXXX&sign=xHy8b0ri-hVozJgkMvV-XXXXXXXXXXXXX="
}
]
}

Originally created by @hirofratica on GitHub (Mar 6, 2025). ### 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 1.0.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce In the latest version of Dify, the “HTTP request” block returns an empty body when making a GET request to an RSS feed URL. This issue was not present in version 0.15.3, where the body contained the expected RSS feed content. 1. Use the “HTTP request” block in a Dify workflow. 2. Set the method to GET. 3. Use the following RSS feed URL as the request URL example : https://www.soumu.go.jp/news.rdf Additional Information • This issue occurs consistently when requesting RSS feeds. • It was working correctly in version 0.15.3. • The headers confirm that the response contains data (content-length: 13362), but the body is empty. • The content appears to be stored as a file instead, which is not the expected behavior. ### ✔️ Expected Behavior The response body should contain the RSS feed content, as it did in version 0.15.3. ### ❌ Actual Behavior { "status_code": 200, "body": "", "headers": { "content-type": "text/xml", "content-length": "13362", "connection": "keep-alive", "server": "Apache", "date": "Fri, 07 Mar 2025 01:49:25 GMT", "x-xss-protection": "1; mode=block", "accept-ranges": "bytes", "x-content-type-options": "nosniff", "etag": "\"3432-62fb62e8cf08d\"", "last-modified": "Fri, 07 Mar 2025 01:02:51 GMT", "x-frame-options": "deny", "x-iij-cache": "HIT" }, "files": [ { "dify_model_identity": "__dify__file__", "id": null, "tenant_id": "69f34d1a-7fcf-4528-b693-65b1e388e362", "type": "document", "transfer_method": "tool_file", "remote_url": null, "related_id": "8ef3d7e5-9568-45a0-9173-042dccd40b8b", "filename": "xxxxxxxxxx.xml", "extension": ".xml", "mime_type": "text/xml", "size": 13362, "url": "/files/tools/8ef3d7e5-9568-45a0-9173-xxxxxxxxx.xml?timestamp=1741312286&nonce=XXXXXXXXXXXX&sign=xHy8b0ri-hVozJgkMvV-XXXXXXXXXXXXX=" } ] }
yindo added the 🐞 bug label 2026-02-21 18:37:22 -05:00
yindo closed this issue 2026-02-21 18:37:22 -05:00
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#9654
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?