Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: url should start with http:// or https:// #12573

Closed
5 tasks done
lucaseatp opened this issue Jan 9, 2025 · 3 comments
Closed
5 tasks done

bug: url should start with http:// or https:// #12573

lucaseatp opened this issue Jan 9, 2025 · 3 comments
Labels
🐞 bug Something isn't working

Comments

@lucaseatp
Copy link

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.15.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

previous workflows were active and running. after upgrading to 0.15.0, I get this error: url should start with http:// or https://
image below:
image

the link is correct, as it ever was. I use variables to run it dynamically, when I use the link as a string, not a variable, it works.

also I get the same issue using the environment variables or conversation variables

✔️ Expected Behavior

flow run normally

❌ Actual Behavior

broke workflow

@dosubot dosubot bot added the 🐞 bug Something isn't working label Jan 9, 2025
Copy link

dosubot bot commented Jan 9, 2025

In Dify version 0.15.0, there is a known issue related to URL handling, particularly when using variables. This version introduced a change that affects how URLs are validated, requiring them to explicitly start with "http://" or "https://". This issue can occur when URLs are constructed dynamically using variables, as you've described.

To address this, ensure that the variables used to construct URLs are correctly formatted and include the necessary protocol prefix. If the issue persists, consider checking if there are any updates or patches available for version 0.15.0 that might resolve this validation problem. Additionally, you might want to verify that the CONSOLE_WEB_URL environment variable is set correctly, as this was a related issue in this version [1].

To continue talking to Dosu, mention @dosu.


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

@lucaseatp
Copy link
Author

lucaseatp commented Jan 9, 2025

all urls already start with https://, what else should be done? @dosubot

@yihong0618
Copy link
Contributor

fixed int #12452

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants