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.
