Frun1na opened a new issue, #4947: URL: https://github.com/apache/rocketmq-dashboard/issues/4947
### Before Creating the Bug Report - [x] I have searched the [open issues](https://github.com/apache/rocketmq-dashboard/issues) of this repository and believe that this is not a duplicate. - [x] This is a defect in RocketMQ Studio, not a usage question and not a defect in another Apache RocketMQ repository. - [x] I can reproduce this on the current `master` branch, or I have stated the exact version I am running below. ### Studio Version branch: `rocketmq-studio` git commit id: `1ef5d860` (upstream tip at the time of the report) deployed as: built from source ### Runtime Environment Verified by code tracing and unit tests on `rocketmq-studio` @ `1ef5d860` (vitest for `web/`, JUnit for `server/`), not against a specific browser or deployment. ### Connected RocketMQ Cluster Not cluster-specific: the defect lives in the code path and reproduces on any deployment where the trigger condition below holds. ### Describe the Bug The plain-HTTP private-network support only matches literal IP addresses. An intranet deployment addressed by DNS name (`http://studio.internal:8080`) is rejected with 'studio server must use HTTPS' even though the name resolves exclusively to RFC1918 addresses, which contradicts the intent that plain HTTP is allowed for private-network Studio endpoints. ### Steps to Reproduce 1. Point `--server` at an intranet hostname that resolves to a private IP (e.g. `http://studio.internal:6789`). 2. rmqctl rejects the target and demands HTTPS. ### What Did You Expect to See? Hostnames whose resolution is entirely private/loopback/link-local are accepted for plain HTTP; anything public, mixed or unresolvable still requires HTTPS. ### What Did You See Instead? Only literal private IPs work; intranet DNS names are forced onto HTTPS. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
