Background

A client wants to have two separate apps with the same domain name but different sub-paths to redirect. For example, app A would be http://myapp.mycompany.com/app-a and app B would be [http://myapp.mycompany.com/app-](<http://myapp.mycompany.com/app-a>)b.

After we configured the Nginx file to let the sub-path proxy to the right application, we met several more barriers:

1. The 2 applications override the cookie for each other. the 2 apps write cookies (XSESSIONID, xaid in it) into the same place. As a result, every time application A logged in, the application B will be kicked out. (I solved it by adding a specific path to the cookie.)
2. The cookie that starts with __HOST- prefix has the same path /. (I solved it by disabling the __Host- prefix, making it non-effective.)

So I did an experiment to find out how to solve the problem. This article logs the whole detailed process of my experiment, from which you will learn how to implement the sub-paths for different applications.

Detailed Process of the Experiment

• Create 2 Mendix applications. (I am using MX v9.24.2)
• Change hosts, routine domain sub-path-test.local to 127.0.0.1 .
• Install and configure Nginx.
• [If needed], change the application index.html file to resolve dojo errors. Conclusion: Don’t need to do any change on the application in my experiment.

Result

After the process, you got the final result as the video below.

Each applications saves the cookie to the sub-path of its own, without effect on other applications.

Untitled

Refs

1. Method from Wengao Liu：Comparing 728194e79eb0e452c922d8e4ceb596ecf94d03c8...5a9b1ae3108d0f5e8762b5e1fd673f8ff6a24e2f · engalar/docker-mendix-buildpack (github.com)
2. Methods from SAIC：QMS负载均衡
3. naming conventions - Why do many sites name cookies with a leading underscore? - Stack Overflow
4. security - remove specific cookie in nginx reverse proxy - Stack Overflow