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

Add permission verification field in image transmission during API conversation #3771

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

Originally created by @gongqibaba on GitHub (May 27, 2024).

Originally assigned to: @takatost on GitHub.

Self Checks

  • 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).
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing?

yes

2. Describe the feature you'd like to see

The interfaces currently used for conversations using APIs are as follows
curl -X POST 'https://api.dify.ai/v1/chat-messages' \ --header 'Authorization: Bearer {api_key}' \ --header 'Content-Type: application/json' \ --data-raw '{ "inputs": {}, "query": "What are the specs of the iPhone 13 Pro Max?", "response_mode": "streaming", "conversation_id": "", "user": "abc-123", "files": [ { "type": "image", "transfer_method": "remote_url", "url": "https://cloud.dify.ai/logo/logo-site.png" } ] }'
I would like to add an authentication field in the URL field of the file that allows for custom names, as for businesses, accessing most data, including images, requires permission verification to ensure data security. Later on, I believe that Dify will definitely support voice and video transmission. If permission verification is not performed when calling APIs for such transmission, I think there may be some problems.

3. How will this feature improve your workflow or experience?

yes

4. Additional context or comments

The interfaces currently used for conversations using APIs are as follows

5. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @gongqibaba on GitHub (May 27, 2024). Originally assigned to: @takatost on GitHub. ### Self Checks - [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] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? yes ### 2. Describe the feature you'd like to see The interfaces currently used for conversations using APIs are as follows `curl -X POST 'https://api.dify.ai/v1/chat-messages' \ --header 'Authorization: Bearer {api_key}' \ --header 'Content-Type: application/json' \ --data-raw '{ "inputs": {}, "query": "What are the specs of the iPhone 13 Pro Max?", "response_mode": "streaming", "conversation_id": "", "user": "abc-123", "files": [ { "type": "image", "transfer_method": "remote_url", "url": "https://cloud.dify.ai/logo/logo-site.png" } ] }'` I would like to add an authentication field in the URL field of the file that allows for custom names, as for businesses, accessing most data, including images, requires permission verification to ensure data security. Later on, I believe that Dify will definitely support voice and video transmission. If permission verification is not performed when calling APIs for such transmission, I think there may be some problems. ### 3. How will this feature improve your workflow or experience? yes ### 4. Additional context or comments The interfaces currently used for conversations using APIs are as follows ### 5. Can you help us with this feature? - [X] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 18:01:51 -05:00
yindo closed this issue 2026-02-21 18:01:51 -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 💪 enhancement
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#3771
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?