langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 03:55:25 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

HTTP Node Fails to Handle Standard GET Requests (e.g. HTTPS API Endpoints) #8809

New Issue
Closed
opened 2026-02-21 18:27:49 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 18:27:49 -05:00
Owner
Copy Link
Copy Source

Originally created by @jaguarliuu on GitHub (Mar 1, 2025).

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

1.0.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Description​
When using the HTTP node to access common API endpoints via HTTPS GET requests, the node returns raw request headers instead of proper responses. This occurs even when the same requests work perfectly in Postman and browsers.

Affected Endpoint​
GET https://wp.upx8.com/api.php

Observed Behavior​

json
{
"request": "GET /api.php HTTP/1.1\r\nHost: wp.upx8.com\r\n\r\n"
}

Reproduction Steps​

Create new workflow with HTTP node
Configure node with:
Method: GET
URL: https://wp.upx8.com/api.php
Execute workflow

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @jaguarliuu on GitHub (Mar 1, 2025). ### 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 1.0.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce **Description​** When using the HTTP node to access common API endpoints via HTTPS GET requests, the node returns raw request headers instead of proper responses. This occurs even when the same requests work perfectly in Postman and browsers. **Affected Endpoint​** GET https://wp.upx8.com/api.php **Observed Behavior​** json { "request": "GET /api.php HTTP/1.1\r\nHost: wp.upx8.com\r\n\r\n" } **Reproduction Steps​** Create new workflow with HTTP node Configure node with: Method: GET URL: https://wp.upx8.com/api.php Execute workflow ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 18:27:49 -05:00
yindo closed this issue 2026-02-21 18:27:49 -05:00
yindo commented 2026-02-21 18:27:49 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 1, 2025):

The issue you're experiencing with the HTTP node in Dify when handling HTTPS GET requests might be related to known issues with HTTPS requests, especially when using non-standard ports or incorrect proxy configurations. Here are a few steps you can take to troubleshoot and potentially resolve the issue:

  1. Check Proxy Configuration: Ensure that your proxy is correctly configured to handle HTTPS traffic. Incorrect configurations can lead to protocol mismatches, resulting in errors like sending a plain HTTP request to an HTTPS port.

  2. Squid Configuration: If you're running Dify in Docker, verify that your domain is listed in the squid.conf file. This is necessary for handling requests to HTTPS URLs with non-standard ports, which might otherwise return a 403 Forbidden error.

  3. Curl Tests: Run curl tests from inside the Docker container to see if the requests succeed there. This can help identify if the issue is specific to the HTTP node or a broader network configuration problem.

These steps address common issues related to HTTPS requests in Dify's HTTP node. If the problem persists, further investigation into the specific network and server configurations might be necessary.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Mar 1, 2025): <!-- Answer --> The issue you're experiencing with the HTTP node in Dify when handling HTTPS GET requests might be related to known issues with HTTPS requests, especially when using non-standard ports or incorrect proxy configurations. Here are a few steps you can take to troubleshoot and potentially resolve the issue: 1. **Check Proxy Configuration**: Ensure that your proxy is correctly configured to handle HTTPS traffic. Incorrect configurations can lead to protocol mismatches, resulting in errors like sending a plain HTTP request to an HTTPS port. 2. **Squid Configuration**: If you're running Dify in Docker, verify that your domain is listed in the `squid.conf` file. This is necessary for handling requests to HTTPS URLs with non-standard ports, which might otherwise return a 403 Forbidden error. 3. **Curl Tests**: Run curl tests from inside the Docker container to see if the requests succeed there. This can help identify if the issue is specific to the HTTP node or a broader network configuration problem. These steps address common issues related to HTTPS requests in Dify's HTTP node. If the problem persists, further investigation into the specific network and server configurations might be necessary. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/05464953-091f-47a3-b55c-5406f18e379c?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/05464953-091f-47a3-b55c-5406f18e379c?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/05464953-091f-47a3-b55c-5406f18e379c?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/05464953-091f-47a3-b55c-5406f18e379c?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/05464953-091f-47a3-b55c-5406f18e379c?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/05464953-091f-47a3-b55c-5406f18e379c?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/05464953-091f-47a3-b55c-5406f18e379c?feedback_type=other)</sup>
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#8809
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?