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

Image url not working #6496

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

Originally created by @xfanwu on GitHub (Nov 1, 2024).

Originally assigned to: @laipz8200 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

Cloud latest

Cloud or Self Hosted

Cloud

Steps to reproduce

I've set up an optional image input in my chat flow, but I'm encountering an error when pasting URLs from Firebase Storage.
I've tested with various images from different buckets, but the issue persists. I don't believe it's related to Firebase, but I haven't been able to reproduce the issue with other services.

Here's an example URL causing the problem:
https://firebasestorage.googleapis.com/v0/b/chance-app-7b166.appspot.com/o/test%2F%E4%B8%8B%E8%BD%BD%20(1).jpeg?alt=media&token=19cddfa5-d594-467f-a171-a45020289736

image

✔️ Expected Behavior

The url should be passed into the flow

❌ Actual Behavior

Error encountered.

Originally created by @xfanwu on GitHub (Nov 1, 2024). Originally assigned to: @laipz8200 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 Cloud latest ### Cloud or Self Hosted Cloud ### Steps to reproduce I've set up an optional image input in my chat flow, but I'm encountering an error when pasting URLs from Firebase Storage. I've tested with various images from different buckets, but the issue persists. I don't believe it's related to Firebase, but I haven't been able to reproduce the issue with other services. Here's an example URL causing the problem: `https://firebasestorage.googleapis.com/v0/b/chance-app-7b166.appspot.com/o/test%2F%E4%B8%8B%E8%BD%BD%20(1).jpeg?alt=media&token=19cddfa5-d594-467f-a171-a45020289736` <img width="317" alt="image" src="https://github.com/user-attachments/assets/a657e720-ae61-4727-86ae-b55544cca231"> ### ✔️ Expected Behavior The url should be passed into the flow ### ❌ Actual Behavior Error encountered.
yindo added the 🐞 bug label 2026-02-21 18:16:00 -05:00
yindo closed this issue 2026-02-21 18:16:00 -05:00
yindo commented 2026-02-21 18:16:01 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 1, 2024):

I found a similar unsolved discussion regarding issues with uploading images via API in Dify's workflow [1].

For image URLs to be accepted in Dify's chat flow, ensure that the files parameter in the request body includes an object with the following properties:

  • type: Must be set to image.
  • transfer_method: Must be set to remote_url.
  • url: The actual image URL.

Example:

"files": [
  {
    "type": "image",
    "transfer_method": "remote_url",
    "url": "https://example.com/image.png"
  }
]

If the issue persists specifically with Firebase Storage URLs, it might be related to access control settings or URL formatting. Ensure that the URLs are publicly accessible and correctly formatted. If you continue to face issues, consider checking any specific security settings in Firebase that might restrict access to the images.

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Nov 1, 2024): <!-- Answer --> I found a similar unsolved discussion regarding issues with uploading images via API in Dify's workflow <sup>[[1]](https://github.com/langgenius/dify/discussions/7482)</sup>. For image URLs to be accepted in Dify's chat flow, ensure that the `files` parameter in the request body includes an object with the following properties: - `type`: Must be set to `image`. - `transfer_method`: Must be set to `remote_url`. - `url`: The actual image URL. Example: ```json "files": [ { "type": "image", "transfer_method": "remote_url", "url": "https://example.com/image.png" } ] ``` If the issue persists specifically with Firebase Storage URLs, it might be related to access control settings or URL formatting. Ensure that the URLs are publicly accessible and correctly formatted. If you continue to face issues, consider checking any specific security settings in Firebase that might restrict access to the images. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:16:01 -05:00
Author
Owner
Copy Link
Copy Source

@laipz8200 commented on GitHub (Nov 1, 2024):

This issue was caused by our CSP, but it's already fixed in our main branch. Just hang tight while we finish testing, and it will be updated to the Cloud version soon!

@laipz8200 commented on GitHub (Nov 1, 2024): This issue was caused by our CSP, but it's already fixed in our main branch. Just hang tight while we finish testing, and it will be updated to the Cloud version soon!
yindo commented 2026-02-21 18:16:01 -05:00
Author
Owner
Copy Link
Copy Source

@xfanwu commented on GitHub (Nov 2, 2024):

@laipz8200 Thank you for the prompt reply.

There is another error when use the 'upload file' s' image.url. Is it a known issue as well?

image

I was wondering if there’s a schedule for when the fix will be updated. Our app relies on this bug fix, so any information on the timeline would be greatly appreciated.

@xfanwu commented on GitHub (Nov 2, 2024): @laipz8200 Thank you for the prompt reply. There is another error when use the 'upload file' s' image.url. Is it a known issue as well? <img width="408" alt="image" src="https://github.com/user-attachments/assets/3f86ee4e-e253-481c-a48c-411a39497640"> I was wondering if there’s a schedule for when the fix will be updated. Our app relies on this bug fix, so any information on the timeline would be greatly appreciated.
yindo commented 2026-02-21 18:16:01 -05:00
Author
Owner
Copy Link
Copy Source

@laipz8200 commented on GitHub (Nov 2, 2024):

@laipz8200 Thank you for the prompt reply.

There is another error when use the 'upload file' s' image.url. Is it a known issue as well?
image

I was wondering if there’s a schedule for when the fix will be updated. Our app relies on this bug fix, so any information on the timeline would be greatly appreciated.

We don't support using the file's signed URL (visible in the log panel). The file.url property refers to the remote_url and only exists when a file is uploaded via a link.

This CSP issue will be fixed in the next release, which is scheduled for next week.

@laipz8200 commented on GitHub (Nov 2, 2024): > @laipz8200 Thank you for the prompt reply. > > There is another error when use the 'upload file' s' image.url. Is it a known issue as well? > <img alt="image" width="408" src="https://private-user-images.githubusercontent.com/6542647/382466661-3f86ee4e-e253-481c-a48c-411a39497640.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzA1NDY1MTcsIm5iZiI6MTczMDU0NjIxNywicGF0aCI6Ii82NTQyNjQ3LzM4MjQ2NjY2MS0zZjg2ZWU0ZS1lMjUzLTQ4MWMtYTQ4Yy00MTFhMzk0OTc2NDAucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MTEwMiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDExMDJUMTExNjU3WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9Y2FkZTI5Yjk2Mzc4OWNlNzg5MGEwZTA5MzljMTI0ZmMzMGI5YjMzM2Q0MGIyM2Y5MmFkMmU2MjNiMWQwMjZlZiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.DFkXhxw5ynpNz61QJAbnRqZu7MZsf9bzDM9obtuge5c"> > > I was wondering if there’s a schedule for when the fix will be updated. Our app relies on this bug fix, so any information on the timeline would be greatly appreciated. We don't support using the file's signed URL (visible in the log panel). The file.url property refers to the remote_url and only exists when a file is uploaded via a link. This CSP issue will be fixed in the next release, which is scheduled for next week.
yindo commented 2026-02-21 18:16:01 -05:00
Author
Owner
Copy Link
Copy Source

@viniciustrndd commented on GitHub (Nov 4, 2024):

@laipz8200, When I use markdown, it logs correctly:

{
"answer": "Great! Here are some compositions with the clay seagulls:\n\nComposition with 2G and 1P\n\nComposition with 4G and 2P\n\nComposition with 4G and 6P\n\nThese handcrafted pieces bring a special touch and can fit into various decoration styles. Did any of these compositions catch your attention? 😊",
"files": []
}

But in the viewer, the image does not appear or load:

Captura de Tela 2024-11-05 às 00 08 31

@viniciustrndd commented on GitHub (Nov 4, 2024): @laipz8200, When I use markdown, it logs correctly: { "answer": "Great! Here are some compositions with the clay seagulls:\n\n![Composition with 2G and 1P](https://<site>/gaivotas-2G1P-.jpg)\n\n![Composition with 4G and 2P](https://<site>/gaivotas-4g2p.jpeg)\n\n![Composition with 4G and 6P](https://<site>/gaivotas-4G6P.jpeg)\n\nThese handcrafted pieces bring a special touch and can fit into various decoration styles. Did any of these compositions catch your attention? 😊", "files": [] } But in the viewer, the image does not appear or load: ![Captura de Tela 2024-11-05 às 00 08 31](https://github.com/user-attachments/assets/6d1c38a5-7634-4f03-bd20-9e6de4a02477)
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#6496
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?