You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
test-stack-up.sh mendix_at() false negative: a branded login.html and the Mendix 11 index.html carry none of mxui / mx-name / Mendix / mxclientsystem #514
Replace theme/web/login.html with a custom page (no Mendix text) on Mendix 11.12.5; bin/test-stack-up.sh --check reports the app not serving while it serves 200; verify-module skips every runtime instrument
Expected
The stack check recognises a running Mendix 11 app whose login page is branded
Actual
mendix_at() looks only for page text (mxui, mx-name, Mendix, mxclientsystem) in /login.html or /index.html; a custom login.html and the Mendix 11 index.html carry none, so --check says the app is not serving while it returns 200, and verify-module skips every runtime instrument. Retest on master 96e3553: test-stack-up.sh:188-199 and app-restart.sh:110-116 use the same text markers
Workaround
Add a generator meta tag with the value Mendix to theme/web/login.html
Fixed for test-stack-up in #568: mendix_at falls back to /mxclientsystem/mxui/mxui.js, requiring a 200, a JavaScript content type and a non-HTML body, so a branded login and the Mendix 11 index are found while an SPA catch-all is not. The same fallback in app-restart.sh is on the roadmap: #579.
Activity
MendixMau commentedon Oct 26, 2026
Fixed for test-stack-up in #568:
mendix_atfalls back to/mxclientsystem/mxui/mxui.js, requiring a 200, a JavaScript content type and a non-HTML body, so a branded login and the Mendix 11 index are found while an SPA catch-all is not. The same fallback inapp-restart.shis on the roadmap: #579.Generated by Claude Code