this makes it impossible to use with the standalone controller over http.
Contributor guide
Tech stack
javascriptnodejs
Domain
apibackend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic JavaScriptUnderstanding of HTTP/HTTPS
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
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.
