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

http module or python request don't support https #15082

New Issue
Closed
opened 2026-02-21 19:20:06 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 19:20:06 -05:00
Owner
Copy Link
Copy Source

Originally created by @xxexplorer on GitHub (Jul 2, 2025).

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.

i need to call https interfcae in dify workflow, i try to use http module and python request in work flow,but both get wrong 403 forbidden。

on the same server，i use curl -v -k <target_url>, it's successful , but dify can't.
i use docker-compose start the dify system, and i try to change some configuration in docker-compose.yaml to ignore ssl verify，but usless。

so i want to know how to ignore ssl verify or use ssl and how to configure the ssl cert.

appreciate for answer,thanks.

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 @xxexplorer on GitHub (Jul 2, 2025). ### 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. i need to call https interfcae in dify workflow, i try to use http module and python request in work flow,but both get wrong 403 forbidden。 on the same server，i use curl -v -k <target_url>, it's successful , but dify can't. i use docker-compose start the dify system, and i try to change some configuration in docker-compose.yaml to ignore ssl verify，but usless。 so i want to know how to ignore ssl verify or use ssl and how to configure the ssl cert. appreciate for answer,thanks. ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 🙋‍♂️ question label 2026-02-21 19:20:06 -05:00
yindo closed this issue 2026-02-21 19:20:06 -05:00
yindo commented 2026-02-21 19:20:06 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jul 2, 2025):

Dify workflows use the httpx library for HTTP/HTTPS requests, and SSL verification is controlled by the ssl_verify setting. You can disable SSL verification (like curl -k) in two ways:

  1. In the HTTP Request node of your workflow, set the ssl_verify option to False. This disables SSL verification for that specific request.
  2. To disable SSL verification globally for all HTTP requests in Dify, set the environment variable HTTP_REQUEST_NODE_SSL_VERIFY=False in your docker-compose.yaml or .env file, then restart your containers. This will apply to all HTTP Request nodes by default source source.

Dify does not currently support specifying a custom CA bundle or certificate file directly—only the boolean skip/verify toggle is available. If you need to trust a custom CA, you would have to add it to the system trust store inside the Docker container.

If you still get a 403 Forbidden after disabling SSL verification, double-check if the target service expects specific headers, authentication, or user-agent strings, as curl and httpx may send different defaults.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

@dosubot[bot] commented on GitHub (Jul 2, 2025): <!-- Answer --> Dify workflows use the httpx library for HTTP/HTTPS requests, and SSL verification is controlled by the ssl_verify setting. You can disable SSL verification (like curl -k) in two ways: 1. In the HTTP Request node of your workflow, set the ssl_verify option to False. This disables SSL verification for that specific request. 2. To disable SSL verification globally for all HTTP requests in Dify, set the environment variable HTTP_REQUEST_NODE_SSL_VERIFY=False in your docker-compose.yaml or .env file, then restart your containers. This will apply to all HTTP Request nodes by default [source](https://github.com/langgenius/dify/blob/e17b33e0049c47535c355e7371e99adde074557c/api/configs/feature/__init__.py) [source](https://github.com/langgenius/dify/pull/21248). Dify does not currently support specifying a custom CA bundle or certificate file directly—only the boolean skip/verify toggle is available. If you need to trust a custom CA, you would have to add it to the system trust store inside the Docker container. If you still get a 403 Forbidden after disabling SSL verification, double-check if the target service expects specific headers, authentication, or user-agent strings, as curl and httpx may send different defaults. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/d10b5b7a-e46b-4cf2-8aa7-20288b08c96e?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/d10b5b7a-e46b-4cf2-8aa7-20288b08c96e?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/d10b5b7a-e46b-4cf2-8aa7-20288b08c96e?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/d10b5b7a-e46b-4cf2-8aa7-20288b08c96e?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/d10b5b7a-e46b-4cf2-8aa7-20288b08c96e?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/d10b5b7a-e46b-4cf2-8aa7-20288b08c96e?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/d10b5b7a-e46b-4cf2-8aa7-20288b08c96e?feedback_type=other)</sup>&nbsp;&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/21853)
yindo commented 2026-02-21 19:20:06 -05:00
Author
Owner
Copy Link
Copy Source

@xxexplorer commented on GitHub (Jul 2, 2025):

i use dify 0.8.2 version
can you show how to set the ssl_verify option to false in dify?
i add HTTP_REQUEST_NODE_SSL_VERIFY=False in .env file and restart containers, is still usless @crazywoola

@xxexplorer commented on GitHub (Jul 2, 2025): i use dify 0.8.2 version can you show how to set the ssl_verify option to false in dify? i add HTTP_REQUEST_NODE_SSL_VERIFY=False in .env file and restart containers, is still usless @crazywoola
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 🙋‍♂️ question
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#15082
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?