Repository navigation
docs(run): the runtime does not derive a root URL from the bind address - #1383
Merged
Merged
Conversation
Measured on 11.12.1 with a blank app (HSQLDB) and an after-startup microflow logging Core.getConfiguration().getApplicationRootUrl(): default (127.0.0.1) -> null --listen-addr 0.0.0.0 -> null 0.0.0.0 + --runtime-setting ApplicationRootUrl=http://192.0.2.2:8080/ -> http://192.0.2.2:8080/ So the claim, in #1249's help text and in two older comments, that the runtime derives its root URL from the listen address is false: unset stays unset. The wildcard warning, flag help, docs rows and CHANGELOG now say that instead. Behaviour is unchanged. Also verified live: under 0.0.0.0 the app answers 200 on the LAN address and loopback, the admin API only on loopback; under a single interface address mxcli dials that address (loopback refuses) and the admin API stays on loopback. `::` could not be measured: this container has no IPv6 (AF_INET6 unsupported), and Mendix reports the failed bind as "Runtime port '8080' is already in use". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UBgg5k5sdMTsURKiigb19C
…improvements-b5e8da
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #1381 (
--listen-addr, from mendixlabs#1249). Wording only, no behaviour change.What
The
--listen-addrhelp text, the wildcard-bind warning, two older code comments, the run-local skill, the docs-site page and the CHANGELOG all claimed that with noApplicationRootUrlthe runtime derives one from the listen address. It does not; they now say so.Evidence (live, Mendix 11.12.1, blank app on HSQLDB)
An after-startup microflow logged
Core.getConfiguration().getApplicationRootUrl():127.0.0.1)null--listen-addr 0.0.0.0null0.0.0.0+--runtime-setting ApplicationRootUrl=http://192.0.2.2:8080/http://192.0.2.2:8080/The same runs also verified #1381's behaviour:
0.0.0.0: the app answers 200 on the LAN address and on loopback, the admin API only on loopback, and the network URL is printed.localhost: refused before the build.::could not be measured: this container has no IPv6 at all (AF_INET6unsupported). Mendix reports that failed bind as "Runtime port '8080' is already in use".Checks
go vet,gofmt, and the--listen-addr/ AppURL / warning tests incmd/mxcli/dockerpass.🤖 Generated with Claude Code
https://claude.ai/code/session_01UBgg5k5sdMTsURKiigb19C
Generated by Claude Code