Support URL rewriting with Application Gateway
PathBasedRouting is nice, but not super great without the ability to rewrite paths. I am trying to front a Service Fabric cluster, where multiple HTTP services live on http://+:80, at different path prefixes. Would be nice to use Application Gateway to direct https://api.company.com to http://cluster/api, and https://www.company.com to http://cluster/www
Thank you for all the votes and feedback. We have started work on this and the capability will be supported soon. If you would like to get in touch with us to discuss your scenarios, please fill this form: https://aka.ms/ApplicationGatewayCohort
Sumit Kute commented
I think this is much required feature as on Apps using ARR cannot be ported to App Gateway if URL rewriting feature is not available. At-least a basic rule engine has to be there.
Even a Http to Https Redirect which is a basic requirement cannot achieved. I do not want to use an third-party WAF solution
Wondering when this feature would be supported. We have 50k sub domains that we would like to do URL rewrites on right now we have to service them with VMs because of custom subdomain limit on webapps. I am looking for this feature for SSL. Main reason we have example Shop.User1.contso.com would like to change it to user1.contso.com/shop on rewrite. There is 3rd party products that can do it.
Are there any news about the status about this feature? I think its a really important feature for a reverse proxy.
When this is coming? This is required for Service Fabric Host apps.
Daniel Beaupre commented
Here we are in May 2017, and this is still marked as PLANNED. This is a much needed feature to integrate service fabric with.
Joon du Randt commented
Yes please I really need this facility
Ryan Lin commented
Indeed, this is a very important feature on Application Gateway, no one wants to distinguish the HTTP and HTTPS while typing URL on browser.
Todd Bowman commented
Agreed, URL rewrite is critical for our application as well. Even down to http --> https, this is an important feature.
Ben Gelens commented
Can anyone shim in on this?
We are currently blocked on a project by this functionality not being in place yet.
My customer has this design where their app is broken up into multiple Web apps which must all fall into one root uri namespace due to authentication / authorization provider demands.
So a client would hit the WAF, be served the root.uri and depending on having been authenticated / authorized yes or no, would be send to rout.uri/login which is in fact another web page.
So root.uri/login should be rewritten with login.internal.web or something so the front-ends of the ASE know what to serve up.
We got this working with barracuda WAF appliance but the customer wants application gateway WAF.
Lidvar Kornberg commented
Parag Bharne commented
Without This Support Application Gateway is worthless specially for fabric applications. Redirection for at-least gateway is required from HTTP to HTTPS.
Customer Cannot Enter each Time https manually.
Jordan Yaker commented
What's the status on this? It would make it so that Azure Functions are a bit easier to use as part of client-facing applications.
Tom Bromby commented
It would be great to be able to rewite the HTTP_HOST section of the URI, would assume this could be done with the ARR function of App Gateway's underlying servers