0

I have a bunch of Static Web Apps fronted by an Application Gateway. Each Static Web App is configured to use a Custom Domain (e.g. app1.example.com) which is a subdomain of a wildcard domain listened to by the Application Gateway (e.g. *.example.com)

What approximate configuration do I need from Application Gateway? I can't figure it out ...

Option 1:

  • A single wildcard Listener (*.example.com)
  • A single wildcard Routing Rule (*example.com -> wildcard Backend Pool)
  • A single generic Backend Settings (No overriding host name)
  • A single wildcard Backend Pool (just forward the request)

However this isn't possible because Backend Pools don't let you configure wildcard FQDNs

Option 2:

  • A single wildcard Listener (*.example.com)
  • An explicitly routed Routing Rule based on sub-domain
  • A single generic Backend Settings (No overriding host name)
  • Several Backend Pools

However this isn't possible since Routing Rules cannot be configured for subdomains (they can for paths)

Option 3:

  • A Listener for every subdomain (app1.example.com, app2.example.com etc.)
  • A Routing Rule for every subdomain
  • A single generic Backend Setting (No overriding hostname)
  • A Backend Pool for each subdomain

This is possible but seems really unnecessary and clunky - it also makes me wonder why there even is a wildcard option for the Listener?

Brendan
  • 153

0 Answers0