Rule Engine Configuration: Add "Prepend" as a redirect destination path option
With the current Rule Engine Configuration feature set, developers only have the option to Replace or Preserve the target path when performing a route configuration redirect override. These two options are rigid, and as such, significantly limit the capabilities of Azure Front Door; adding a Prepend option would significantly add more flexibility to Azure Front Door - while keeping it easy for developers to use.
Attached is a mock-up of how this functionality would be utilized within the Rule Engine Configuration blade.
In this mock-up, a rule is configured so that any request to http://somewebsite.com with a path not starting with /en-us or /es-mx, will automatically have /es-mx prepended to it with a 302 redirect performed.
Sample test cases:
- http://somewebsite.com/sample-path would become http://somewebsite.com/es-mx/sample-path
- http://somewebsite.com/en-us/sample-path would stay as http://somewebsite.com/en-us/sample-path
- http://somewebsite.com/es-mx/sample-path would stay as http://somewebsite.com/es-mx/sample-path
- http://somewebsite.com/fr-fr/sample-path would become http://somewebsite.com/es-mx/fr-fr/sample-path
This approach would be easier and faster for the AFD team to implement than regexes, while still providing additional flexibility and features needed by developers.