简体繁体 English

使用Azure Web App重写ISAPI

[英]ISAPI Rewrite With Azure Web App

原文 2015-06-08 10:44:53 8 1 asp.net/ .htaccess/ azure/ azure-web-sites/ isapi-rewrite

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. 但是我有一个现有的.NET网站，我正在从专用的EC2服务器迁移到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 ). 但是，此当前站点使用一个.htaccess文件，该文件具有大约200个重定向（ 从旧网址到新网址的301个重定向），该重定向由ISAPI重写（ 已在Win2008服务器上手动安装 ）提供支持。

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 )? 我需要保留这些重定向，但是想知道当迁移到Azure Web App（ 从安装了ISAPI重写的专用服务器上 ）到其他所有人时，.NET应用程序上的永久性URL重定向如何处理吗？

Putting them all in the web.config seems a little odd to me? 把它们全部放在web.config中对我来说有点奇怪吗？ And I don't know how that would affect performance? 而且我不知道这会如何影响性能？

Any advice or pointers would be appreciated as always. 任何建议或指示将一如既往。

1 个解决方案

I always put them in the web.config. 我总是将它们放在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. 如果您认为它太乱了，可以将它们放在单独的文件中，然后使用configSource属性链接到该文件。