this makes it impossible to use with the standalone controller over http.
贡献者指南
技术栈
javascriptnodejs
领域
apibackend
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
2
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
under 1 hour
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Basic JavaScriptUnderstanding of HTTP/HTTPS
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
75
研究方向
The issue is in the file core/routemgmt/common/apigw utils.js at line 608, where the URL is hardcoded to use 'https'. The fix involves using the request's protocol (e.g., req.protocol) or a configuration option to determine whether to use 'http' or 'https'. Check if there are any other places in the same file with similar hardcoded URLs and update them accordingly. No pull requests or comments exist yet, so the fix can be submitted directly.
