ISAPI Rewrite With Azure Web App

1
votes

I'm not sure if this is the best/correct place for this type of question. But I have an existing .NET website which I am moving from our dedicated EC2 server to an Azure Web App.

However, this current site uses an .htaccess file with about 200 redirects (301 from old urls to new ones) which is powered by ISAPI rewrite (Which was installed manually on the Win2008 server).

I need to keep these redirects, but wondering how everyone else deals with permanent Url redirects on .NET applications when moving to an Azure Web App (From a dedicated server that had ISAPI rewrite installed)?

Putting them all in the web.config seems a little odd to me? And I don't know how that would affect performance?

Any advice or pointers would be appreciated as always.

1
asp.net.htaccessazureazure-web-app-serviceisapi-rewrite

1 Answers

2
votes

I always put them in the web.config.
If you think it will be too messy, you can put them in a separate file and use the configSource attribute to link to the file.