Server-side redirects
Accepts a full URL or just the path starting with /.
All of them redirect to the same destination. Accepts a full URL or just the path. The type is detected for each one: end it with / to redirect the whole directory; with no path, only the home page.
Generated rules
.htaccess0 rulesEnter the source and destination URLs to generate the rules.
Paste the rule at the beginning of the .htaccess file, in the site root. Lines starting with # are comments and you can keep them.
In a batch, order matters: rules are evaluated top to bottom and the first match wins. If you mix directories with pages that hang from them, put the specific pages first.
Place the block inside the server { } of the source domain, in your Nginx configuration.
Remember to restart or reload your nginx server.
If your URL has accents, letters from another alphabet, or spaces, follow this guide to redirect with special characters.
Add the rule inside <system.webServer> → <rewrite> → <rules> of the web.config file, in the site root.
Redirect rules in Azure are not created with server syntax like Nginx or Apache, but through the web.config configuration in the site root when using IIS, or through routing rules in .NET or .NET Core web applications.
However, you can apply these rules in a web.config file in IIS, which simulates the redirect functionalities you have described. These rules would live inside the <rules> tag in the <rewrite> section.
Note: the redirect rules generated here are quite simplified and you may need to adjust them to fit your exact needs. Also, remember that you must have the URL Rewrite module installed on your IIS server to use these rules.