Http Node in flow #6374

Closed
opened 2026-02-21 18:15:27 -05:00 by yindo · 6 comments
Owner

Originally created by @nameIsNoPublic on GitHub (Oct 28, 2024).

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

0.10.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

This is "Generating analysis of Twitter account using Chatflow Agent"
image

But This is image in my local
image
My Dify version ls 0.10.1
You can see it in the request as a key https://api.crawlbase.com Omitted

✔️ Expected Behavior

No response

Actual Behavior

No response

Originally created by @nameIsNoPublic on GitHub (Oct 28, 2024). ### 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 0.10.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce This is "Generating analysis of Twitter account using Chatflow Agent" ![image](https://github.com/user-attachments/assets/4ed2a4eb-19ea-4bdc-a1c0-d748bc101068) But This is image in my local ![image](https://github.com/user-attachments/assets/822bebc4-e7dc-4bce-a10e-4689ab552b58) My Dify version ls 0.10.1 You can see it in the request as a key https://api.crawlbase.com Omitted ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo closed this issue 2026-02-21 18:15:27 -05:00
Author
Owner

@nameIsNoPublic commented on GitHub (Oct 28, 2024):

This resulted in a return result of 400, and I carefully reviewed their latest documentation

@nameIsNoPublic commented on GitHub (Oct 28, 2024): This resulted in a return result of 400, and I carefully reviewed their latest documentation
Author
Owner

@nameIsNoPublic commented on GitHub (Oct 28, 2024):

The latest document only includes parameters for " URL" and "token"

@nameIsNoPublic commented on GitHub (Oct 28, 2024): The latest document only includes parameters for " URL" and "token"
Author
Owner

@dosubot[bot] commented on GitHub (Oct 28, 2024):

The 400 error you're encountering when using the HTTP Node in Dify might be due to missing or incorrect parameters in your request to the api.crawlbase.com endpoint. According to the information available, the latest documentation specifies that the parameters required for requests to this endpoint include "URL" and "token". Ensure that these parameters are correctly included in your request.

If the issue persists, double-check that the token is valid and correctly formatted, and that the URL is properly specified. Additionally, verify if there are any other required parameters or headers that might not be documented but are necessary for the request to succeed.

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Oct 28, 2024): <!-- Answer --> The 400 error you're encountering when using the HTTP Node in Dify might be due to missing or incorrect parameters in your request to the `api.crawlbase.com` endpoint. According to the information available, the latest documentation specifies that the parameters required for requests to this endpoint include "URL" and "token". Ensure that these parameters are correctly included in your request. If the issue persists, double-check that the token is valid and correctly formatted, and that the URL is properly specified. Additionally, verify if there are any other required parameters or headers that might not be documented but are necessary for the request to succeed. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
Author
Owner

@nameIsNoPublic commented on GitHub (Oct 28, 2024):

no ,I have already tried it

@nameIsNoPublic commented on GitHub (Oct 28, 2024): no ,I have already tried it
Author
Owner

@nameIsNoPublic commented on GitHub (Oct 28, 2024):

I suggest you check the encoding and decoding of env, as it is possible for me to use plaintext tokens

@nameIsNoPublic commented on GitHub (Oct 28, 2024): I suggest you check the encoding and decoding of env, as it is possible for me to use plaintext tokens
Author
Owner

@dosubot[bot] commented on GitHub (Nov 28, 2024):

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

Issue Summary:

  • You are experiencing a 400 error with the "Generating analysis of Twitter account using Chatflow Agent" feature.
  • This issue occurs in Dify version 0.10.1 within a self-hosted Docker setup.
  • You have confirmed that the "URL" and "token" parameters are correctly included in your request.
  • Despite verifying the token and URL as suggested, the issue persists.
  • You proposed checking the encoding and decoding of environment variables due to the use of plaintext tokens.

Next Steps:

  • Please confirm if this issue is still relevant to the latest version of the Dify repository. If so, you can keep the discussion open by commenting on this issue.
  • Otherwise, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Nov 28, 2024): Hi, @nameIsNoPublic. 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:** - You are experiencing a 400 error with the "Generating analysis of Twitter account using Chatflow Agent" feature. - This issue occurs in Dify version 0.10.1 within a self-hosted Docker setup. - You have confirmed that the "URL" and "token" parameters are correctly included in your request. - Despite verifying the token and URL as suggested, the issue persists. - You proposed checking the encoding and decoding of environment variables due to the use of plaintext tokens. **Next Steps:** - Please confirm if this issue is still relevant to the latest version of the Dify repository. If so, you can keep the discussion open by commenting on this issue. - Otherwise, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#6374