langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-22 12:36:14 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

How to enable HTTPS support for the HTTP request block in Dify. #6153

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

Originally created by @ismasher2000 on GitHub (Oct 17, 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.

My API backend must be based on HTTPS for security compliance purposes, but I cannot find a way to enable HTTPS support for the HTTP Request Block. After testing, it seems that the HTTP Request Block does not support HTTPS at all, which poses certain security risks.

2. Additional context or comments

When connecting to my HTTPS backend API using HTTPS in HTTP Request Block, I get a 403 Forbidden error. If I connect to my HTTPS backend using HTTP in HTTP Request Block, the status is successful, but the return message says: "The plain HTTP request was sent to HTTPS port."

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @ismasher2000 on GitHub (Oct 17, 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. My API backend must be based on HTTPS for security compliance purposes, but I cannot find a way to enable HTTPS support for the HTTP Request Block. After testing, it seems that the HTTP Request Block does not support HTTPS at all, which poses certain security risks. ### 2. Additional context or comments When connecting to my HTTPS backend API using HTTPS in HTTP Request Block, I get a 403 Forbidden error. If I connect to my HTTPS backend using HTTP in HTTP Request Block, the status is successful, but the return message says: "The plain HTTP request was sent to HTTPS port." ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 18:14:18 -05:00
yindo closed this issue 2026-02-21 18:14:18 -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#6153
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?