Reputation: 29
In a web application deployed on several Azure VMs, load is balanced using Application Gateway. The selection of Application Gateway is mainly because the application requires cookie-based session affinity.
For a function in the application, a specific VM in the Backend Pool needs to be chosen. So I think giving the user a different login page URL could help me route things properly.
I've tried using different rules, but since a listener can have only one rule this doesn't work in my case.
What I want to achieve is: https://myapplication/mycontext
While https://myapplication/mycontext/process
What should the configuration of a Path-Based Rule be to achieve this behavior?
Upvotes: 0
Views: 185
Reputation: 1502
You would need to create 2 backend pool, one to server all content (A) and one specific pool for /process requests (B).
Create a path based rule, a default rule to forward /mycontext/* to the backend pool A another rule to forward /mycontext/process/* to another backend pool B.
Upvotes: 0