How to Fix Azure Application Gateway Server Error 502 – stale HTTP rule

This post is about fixing Azure application gateway server error 502, caused by duplicated/stale HTTP rules that referenced differently between the “Rules” session and “Backend pool” session


Similar to the previous post

Under the “Rules” session

Rule names are matched.

Under the “Backend Pool” session

The Fix

Remove the duplicated/stale HTTP rule and create a new one with a DIFFERENT name.

Leave a Comment

Your email address will not be published. Required fields are marked *