Allow multiple hostnames in the same Listener Application Gateway
Sometimes we share differents hostnames with the same web site.
Currently, this means that we have to deploy differents listeners in order to provide access to the same backend pool.
With a 20 listeners limit this solution is a bit expensive...
Would it be possible to add multiple hostnames/sitenames to listener?
Thanks in advance
Antonio J.
shared this idea
Wildcard host names in listeners for Application Gateway v2 is currently in public preview! You can configure host names with wildcard characters (* and ?) and up to 5 host names per listener with comma separated values.
We’d love for you to try it out and provide your valuable feedback. Learn more here – https://aka.ms/wildcardlistenerpreview
7 comments
-
Danny Murphy
commented
I have an application running on 2 Azure servers that serve content based on the domain being accessed. All domains have the same site template but the contents are different
Currently I have 286 domains being served this way on our current WAF solution. Hoping to move to Azure WAF once we can have more hostnames per listener - 100 Would be easiest if possible
-
Rick Mason
commented
The ARM schema for a listener includes a `hostNames` property as an alternative to `hostName`, and it's exposed in the UI if you select Listener Type > Multi-site..
-
Scott Heath
commented
Just another guy waiting for this feature - can we get an update?
-
Maha
commented
Any update on when this feature will be available.
-
Andres Barcenas
commented
When are we expecting this to be completed?
-
Stephen Kowalchuk
commented
bump -- SSL offload for multiple domains (and not covered in a SAN cert but requiring more than one cert) would be a huge benefit. If there is a workaround, I'm sure folks would appreciate hearing about it.
-
Brandon Kearns
commented
We have one IIS server that is planning to host over 10 different websites. Current configuration using the Application Gateway with https redirection would require more than one application gateway. Please allow this configuration!