Replies: 2 comments 1 reply
-
Looks like App Gateway just uses the first rule that matches so whenever it hits *.site.com/* all other rules are ignored. There is a "priority" property on the routing rules but I can't see any annotations that look like they'd set that. Anyone know how to set the priority of the rules? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hi @robs, yes, that's correct. Here is an article explaining the behavior. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hiya,
We had AGIC setup and working fine until we deployed the "production" app which then was intercepting ALL traffic.
These routes were working fine together:
When we deployed the 'prod' site:
Everything was directed to that!
It's like app gateway was using the LEAST specific rule rather than MOST specific.
All of the listeners are multi-site, well, they all have hostname:null and hostnames populated.
Is that an issue with app gateway or the way AGIC updates it?
I can't believe it's how app gateway is supposed to behave with this config.
Thanks,
Rob.
Beta Was this translation helpful? Give feedback.
All reactions