routing
1 Topic
Complicated Application Gateway Setup
Hi, I am looking to set up a complicated application gateway and seem to be struggling to get to get things right and am not sure if it something I am doing wrong or a limitation that I need to work around. What I want to do is have the gateway handle sub domain routing (pretty easy) and path based routing (on it's on pretty easy) and direct the traffic to app service end points (not sure if this is causing the problem due to multi tenancy) The sub domains are used currently to manage our different development environments (eg uat.contoso.com and dev.contoso.com) The path based routing is for the various applications that we run. (uat.contoso.com/application1 and uat.contoso.com/application2) I would love to change some of these things but the routing is legacy and a lot of stakeholders in the organisation are resistant to change. I have tried a few times to set things up the way I believe they should be set up but I get 404 errors or redirects to the app service url (which I am avoiding as I want to create and internal private url not a public one) Any pointers would be appreciated. -GraeSolved2.4KViews0likes5Comments