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

Custom tool permission verification supports multiple headers. #6623

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

Originally created by @danerlt on GitHub (Nov 7, 2024).

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).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

When adding custom tools using Dify, I can only add one header field in the header when making an API call. In my scenario, there are multiple header fields required.
image

I hope to support multiple headers.

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @danerlt on GitHub (Nov 7, 2024). ### 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] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [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? Tell me about your story. When adding custom tools using Dify, I can only add one header field in the header when making an API call. In my scenario, there are multiple header fields required. ![image](https://github.com/user-attachments/assets/21c19c1f-6537-4cc3-9b3e-c6646f3ac0a2) I hope to support multiple headers. ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [X] I am interested in contributing to this feature.
yindo added the 💪 enhancement🔨 feat:tools labels 2026-02-21 18:16:35 -05:00
yindo closed this issue 2026-02-21 18:16:36 -05:00
yindo commented 2026-02-21 18:16:36 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 9, 2024):

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

Issue Summary:

  • Request to add support for multiple headers in API calls for custom tools.
  • Current limitation: only a single header field is supported.
  • You expressed willingness to contribute to this feature.
  • No further comments or activity since the issue was opened.

Next Steps:

  • Is this issue still relevant to the latest version of the Dify repository? If so, please comment to keep the discussion open.
  • If there is no further activity, the issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Dec 9, 2024): Hi, @danerlt. 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:** - Request to add support for multiple headers in API calls for custom tools. - Current limitation: only a single header field is supported. - You expressed willingness to contribute to this feature. - No further comments or activity since the issue was opened. **Next Steps:** - Is this issue still relevant to the latest version of the Dify repository? If so, please comment to keep the discussion open. - If there is no further activity, the issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
yindo commented 2026-02-21 18:16:36 -05:00
Author
Owner
Copy Link
Copy Source

@why-el commented on GitHub (Dec 12, 2024):

Some APIs require more headers. This might be surprising but there are APIs that require a content type always, for instance. With just one header for the API key, we cannot use those tools.

@why-el commented on GitHub (Dec 12, 2024): Some APIs require more headers. This might be surprising but there are APIs that require a content type always, for instance. With just one header for the API key, we cannot use those tools.
yindo commented 2026-02-21 18:16:36 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 12, 2024):

@takatost, the user has indicated that the issue regarding support for multiple headers in API calls is still relevant, as some APIs require additional headers like content type. Could you please assist them with this?

@dosubot[bot] commented on GitHub (Dec 12, 2024): @takatost, the user has indicated that the issue regarding support for multiple headers in API calls is still relevant, as some APIs require additional headers like content type. Could you please assist them with this?
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 🔨 feat:tools
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#6623
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?