Are Microflow URLs in Mendix case-sensitive, and how can I make them work for both lowercase and uppercase URLs?

0
Hello Experts,   I have exposed a microflow as a URL in Mendix and noticed that the URL is case-sensitive.   Example: http://localhost:8081/p/loginpage/en   → works http://localhost:8081/p/LoginPage/en   → does NOT work   The microflow URL is configured in lowercase:loginpage My questions: 1. Are Microflow URLs in Mendix case-sensitive by design? 2. Is this behavior consistent across all environments (local, UAT, production)? 3. Is there a recommended or supported way to make the same Microflow URL work in both cases, for example:   - /p/loginpage/en   - /p/LoginPage/en 4. If this is not supported out of the box, what is the best-practice workaround (duplicate microflow URLs, reverse proxy, custom redirect, etc.)?   Mendix version: 10.24.10  Platform: Web  
asked
2 answers
0

In Mendix, published microflow URLs (/p/…) are basically case-sensitive, so the runtime expects the URL to match exactly. Because of that, /p/loginpage/en works, while /p/LoginPage/en does not, and this is normal behavior across local, UAT, and production. There isn’t a built-in way in Mendix to make these URLs case-insensitive. The easiest and cleanest approach is to pick one format (usually all lowercase) and use it everywhere. If you really need to support different casings, the best workaround is to handle it at the reverse proxy or ingress level by redirecting everything to lowercase before it reaches Mendix. As an alternative inside Mendix, you can publish two microflows with different URL casings that both call the same core microflow, but this does mean a bit more maintenance.

answered
0

Hi Pragadeesh,

 

  1. Yes, Microflow URLs are case-sensitive by design (even though Mendix docs don’t explicitly mention it, they work with exact matching).
  2. Yes, this behavior is consistent across all environments.
  3. I couldn’t find any official recommendation for making them case-insensitive.
  4. Here’s what I would do as a workaround:
    • Create a custom request handler, for example /link (Ref: Request Handlers).
    • In Startup, register this handler via a Java action. It will catch all /link calls, convert the incoming path to lowercase, and then redirect to the correct page or Microflow URL.
    • To avoid open redirect risks, maintain an allow-list of canonical paths you want to support. (Not sure if it is needed)
    • Using aliases inside Mendix is also an option, but managing all possible case combinations can become difficult.

Hope this helps!

answered