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

工作流编排使用HTTP请求时,发起GET请求报403 #504

Open
layoonmietly opened this issue Feb 13, 2025 · 1 comment
Open

工作流编排使用HTTP请求时,发起GET请求报403 #504

layoonmietly opened this issue Feb 13, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@layoonmietly
Copy link

layoonmietly commented Feb 13, 2025

本地使用docker部署,新建一个工作流应用,编排工作流时,使用HTTP请求,配置了GET请求 url、header,在运行时报403,进入docker-ssrf_proxy容器中查看日志,显示:172.18.0.8 TCP_DENIED/403 3792 CONNECT xxxxxx.com - HIER_NONE/- text/html。该GET请求返回的是JSON,后添在header中配置添加了Content-Type: application/json 仍然报,容器内日志,仍然是"172.18.0.8 TCP_DENIED/403 3792 CONNECT xxxxxx.com - HIER_NONE/- text/html";
再补充下:进入docker-ssrf_proxy容器后,使用curl 访问 get请求 是能成功并获取到json数据的,所以排除了网络问题

Copy link

dosubot bot commented Feb 13, 2025

@layoonmietly 你好!我是一个可以帮助你解决bug、回答问题,甚至成为贡献者的机器人。在等待人类维护者的过程中,我可以帮助你。

要解决在本地部署的 Docker 工作流应用中发起 GET 请求时遇到的 403 错误,请确保在请求中包含正确的 Authorization 头。错误信息表明请求由于缺少访问权限而被拒绝,这通常是由于 Authorization 头中的 API 密钥不正确或缺失导致的。

根据文档,Authorization 头的格式应如下:

Authorization: Bearer {API_KEY}

请确保将 {API_KEY} 替换为您的实际 API 密钥。如果 API 密钥不正确或缺失,您将收到 403 错误,并显示无效的授权头格式的错误信息。请仔细检查 API 密钥是否有效并在请求中正确格式化[1]

To continue talking to Dosu, mention @dosu.


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

@dosubot dosubot bot added the bug Something isn't working label Feb 13, 2025
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

1 participant