Linked Questions

Popular Questions

Application Gateway routing URL's to custom ports

Asked by At

We have an Application Gateway operational with the following setup

Backend 1 : Server A, Server B
Backend 2 : Server C

Listener1 - site.com - Port 8888 HTTPS - Backend 1
Listener2 - site.com - Port 3000 HTTPS - Backend 2 
Listener3 - site.com - Port 10001 HTTPS - Backend 1

This is routing correctly when site.com:port is specified however this isn't ideal for the end user to remember to include the port.

What we want to do is

sub.site.com to map to site.com:8888
sub2.site.com to map to site.com:3000
sub3.site.com to map to site.com:10001

OR

site.com/sub to map to site.com:8888
etc

This will allow the users to connect to the service via a friendly URL rather than the port number.

Would a path-based rule with the path as /sub and the HTTP setting as the custom port be sufficient?

Any advice greatly appreciated.

Related Questions