简体   繁体   English

网址重定向 - IIS6 - PHP -> .NET

[英]UrlRedirect - IIS6 - PHP -> .NET

I am looking to move an existing WordPress installation to a custom platform comprised of a .net based blog as well as other new functionality/modules on the site running under IIS6/Win2k3.我希望将现有的 WordPress 安装移动到自定义平台,该平台由基于 .net 的博客以及在 IIS6/Win2k3 下运行的站点上的其他新功能/模块组成。 There are several thousand posts in the existing WordPress site that have been migrated to the new database structure, however, I'd like to preserve the old urls (for search engine sake).现有的 WordPress 站点中有数千个帖子已迁移到新的数据库结构,但是,我想保留旧的 url(为了搜索引擎)。

The application is already using URLRewriting.NET to provide SEO friendly links throughout the site, so I know I can write up a rule to parse/redirect the inbound requests:该应用程序已经在使用 URLRewriting.NET 在整个站点中提供 SEO 友好的链接,所以我知道我可以编写一个规则来解析/重定向入站请求:

http://mydomain.com/index.php/2008/11/20/my-post/ http://mydomain.com/index.php/2008/11/20/my-post/

Would be handled by something like: http://mydomain.com/blog.aspx?slug=my-post&date=2008-11-20将通过以下方式处理: http://mydomain.com/blog.aspx?slug=my-post&date=2008-11-20

To do it this way, I would need to configure the.php extension to be handled by aspnet_isapi.dll.为此,我需要将 .php 扩展配置为由 aspnet_isapi.dll 处理。 Is it possible to have one 'Web Site' configured to handle PHP via aspnet and another 'Web Site' configured to handle PHP using the actual php isapi handler?是否可以将一个“网站”配置为通过 aspnet 处理 PHP,而将另一个“网站”配置为使用实际的 php isapi 处理程序处理 PHP? It would seem possible based on the configuration through IIS Manager, though I suspect the whole 'Web Service Extension' bit would cause a problem.根据 IIS 管理器的配置,这似乎是可能的,尽管我怀疑整个“Web 服务扩展”位会导致问题。

Yes, it's possible to change handler's based on the site.是的,可以根据站点更改处理程序。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM