I have two app services that I use application gateway and route traffic to using URL Routing. For example: api1-app-service api2-app-service I use the Application Gateway with a custom domain in front of it, and route the traffic like this: appgateway-public-ip/d1/explore-> api1-app-service appgateway-public-ip/d2/explore-> api2-app-service I have created a http listener and https listener type and routing rul which is path based /d1/ -> api1-app-service(backend pool and setting and http listener) /d2/ -> api2-app-service(backend pool and setting and https listener) When I try http://<app gateway ip>/d2/explorer it give 502 which is using https listener What am I doing wrong

Application Gateway - With Https Listener

Nitya V 45

I have two app services that I use application gateway and route traffic to using URL Routing.

For example:

api1-app-service
api2-app-service

I use the Application Gateway with a custom domain in front of it, and route the traffic like this:

appgateway-public-ip/d1/explore-> api1-app-service
appgateway-public-ip/d2/explore-> api2-app-service

I have created a http listener and https listener type and routing rul which is path based /d1/-> api1-app-service(backend pool and setting and http listener) /d2/-> api2-app-service(backend pool and setting and https listener)

When I try http://<app gateway ip>/d2/explorer it give 502 which is using https listener

What am I doing wrong

ChaitanyaNaykodi-MSFT 25,841 Reputation points Microsoft Employee

2024-08-13T21:52:31.85+00:00

@Nitya V

Thank you for reaching out.

I understand you have set-up path based routing rule for your App Gateway

From your question you have set-up the paths as /d1/ and /d2/ , can you modify these paths to /d1/* and /d2/* as the wildcard is required to match the /d2/explorer path you are testing with.

Meanwhile 502 Error can be also due backend health probe set-up, can you confirm if the Health Probe set-up for the HTTPS App-service is showing up as healthy? You can follow the steps mentioned here.

Hope this helps! Thanks
Nitya V 45 Reputation points

2024-08-14T10:13:43.5066667+00:00

We have set a custom probe and it showing unhealthy with Cannot connect to backend server. Check whether any NSG/UDR/Firewall is blocking access to the server. Check if application is running on correct port.

No firewall rule/NSG/User defined rule is set
ChaitanyaNaykodi-MSFT 25,841 Reputation points Microsoft Employee

2024-08-15T04:08:12.5833333+00:00

@Nitya V In this case can you check if the path set for custom probe is returning correct response.

By default, an HTTP(S) response with status code between 200 and 399 is considered healthy. You can also follow the troubleshooting steps here

Also in the custom probe set-up check what you have entered as host name, as it is used both as host header and SNI. More details can be found here

Hope this helps! Thanks
Nitya V 45 Reputation points

2024-08-20T10:06:04.62+00:00
The custom probe seems to be fine as

appgateway-public-ip/d1/explore-> api1-app-service - This works

appgateway-public-ip/d2/explore-> api2-app-service - This doesnt

Share via

Application Gateway - With Https Listener

Your answer