The image retrieval function in the knowledge base retrieval section is not working properly
- Dominant language
- TypeScript
- Stars
- 156k
- Forks
- 24.6k
- Avg merge
- 22h 9m
- Merged PRs (30d)
- 610
Description
### Self Checks
- [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542).
- [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, otherwise it will be closed.
- [x] 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :)
- [x] Please do not modify this template :) and fill in all the required fields.
### Dify version
17.1
### Cloud or Self Hosted
Self Hosted (Docker)
### Steps to reproduce
During the process of knowledge base retrieval, it was found that some images could not be rendered normally. Upon examining the returned URLs, there was no difference in structure compared to other URLs that could be rendered. Additionally, the original image was found through a key query in the database. Therefore, there should be no issue with the original image URL. Considering whether it was returned by Dify itself
### ✔️ Expected Behavior
I hope this issue can be resolved as soon as possible
### ❌ Actual Behavior
_No response_
Contributor guide
Research direction
Reproduce the problem in the Dify 17.1 self-hosted Docker setup during knowledge base retrieval, comparing an image that renders with one that does not. Inspect the returned image URLs and the corresponding database records first; done means the affected images render normally through the retrieval flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100