Forum Discussion
Complicated Application Gateway Setup
- Jul 10, 2020
Hi Charbelhanna ,
Thanks for reply.
SOLVED
I ended up solving my issue not through app gateway but through app service. Basically the problem was the HTTP settings needed to be set to override with new host name as it is an app service. This combined with the path based mapping resulted in a virtual path that did not exist. I attempted to use rewriting but that only went so far but setting a virtual path "/appname" to point at "site/wwwroot" and changing the default to point to a dummy folder achieved the outcome. I did need to change my health probes after this but again I would like to point out this was not a health probe issue it was a routing based issue.
Thanks
Did you setup health probes properly?
Hi Youdhbir Singh ,
The health probes are responding with healthy. Correct me if I am wrong but health probes are only there to determine if traffic can be routed to an end point. So if a health probe reports healthy then the application gateway routes traffic. If not then the gateway responds to the client with a 502 error. In this case I am receiving a 404 so it shouldn't be the health probes?
Cheers
Grae