<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.iis.net/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Ruslan&amp;#39;s Blog</title><link>http://blogs.iis.net/ruslany/default.aspx</link><description /><dc:language>en</dc:language><generator>CommunityServer 2007 SP1 (Build: 20510.895)</generator><item><title>URL Rewrite Module - Release to Web</title><link>http://blogs.iis.net/ruslany/archive/2008/11/10/url-rewrite-module-release-to-web.aspx</link><pubDate>Mon, 10 Nov 2008 22:32:11 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:2736677</guid><dc:creator>RuslanY Blog</dc:creator><slash:comments>0</slash:comments><description>Today IIS team has made the URL Rewrite Module for IIS 7.0 Release To Web (RTW) available for download. This is a final, production-ready release that is officially supported by Microsoft. Install the URL Rewrite Module for IIS 7.0 RTW today! Microsoft URL Rewrite Module for IIS 7.0 RTW (x86) Microsoft URL Rewrite Module for IIS 7.0 RTW (x64) Upgrade from Go Live release If you already have Go Live release of URL Rewrite module installed then the installation package will upgrade it to RTW release. All rewrite rules in applicationHost.config and web.config files will be preserved. Note that system reboot may be necessary when upgrading from Go Live to RTW release. ASP.NET update The installer for URL Rewrite module includes an update for ASP...(&lt;a href="http://blogs.iis.net/ruslany/archive/2008/11/10/url-rewrite-module-release-to-web.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.iis.net/aggbug.aspx?PostID=2736677" width="1" height="1"&gt;</description><category domain="http://blogs.iis.net/ruslany/archive/tags/IIS+News+Item/default.aspx">IIS News Item</category><category domain="http://blogs.iis.net/ruslany/archive/tags/URLRewrite/default.aspx">URLRewrite</category></item><item><title>Major revision of FastCGI/PHP article on IIS.NET</title><link>http://blogs.iis.net/ruslany/archive/2008/10/31/major-revision-of-fastcgi-php-article-on-iis-net.aspx</link><pubDate>Fri, 31 Oct 2008 21:27:05 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:2717940</guid><dc:creator>RuslanY Blog</dc:creator><slash:comments>0</slash:comments><description>Since the time we have published the article about installing FastCGI and PHP on IIS 7.0 it has become one of the most popular articles on http://learn.iis.net . Also it has received a lot of comments from site visitors. Today, we are publishing the updated version of this article that contains more up-to-date information and addresses most of the feedback from community. Here is what this article includes now: Overview Enabling FastCGI support in IIS 7.0 Windows Server 2008 Windows Vista SP1 Update for the FastCGI module Administration Pack for IIS 7.0 Install and Configure PHP Configure IIS to handle PHP requests Using IIS Manager Using command line Best practices for configuring FastCGI and PHP Security Isolation Process recycling PHP versioning...(&lt;a href="http://blogs.iis.net/ruslany/archive/2008/10/31/major-revision-of-fastcgi-php-article-on-iis-net.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.iis.net/aggbug.aspx?PostID=2717940" width="1" height="1"&gt;</description><category domain="http://blogs.iis.net/ruslany/archive/tags/PHP/default.aspx">PHP</category><category domain="http://blogs.iis.net/ruslany/archive/tags/FastCGI/default.aspx">FastCGI</category></item><item><title>Debug and troubleshoot rewrite rules easily</title><link>http://blogs.iis.net/ruslany/archive/2008/10/30/debug-and-troubleshoot-rewrite-rules-easily.aspx</link><pubDate>Thu, 30 Oct 2008 05:13:28 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:2713746</guid><dc:creator>RuslanY Blog</dc:creator><slash:comments>0</slash:comments><description>One of the very cool features of URL Rewrite Module is its integration with IIS Failed Request Tracing . When you have rewrite rules that do not work the way you expect them to work - enable Failed Request Tracing and you will get the entire history of how rewrite rules were applied on the requested URL. I use Failed Request Tracing all the time and it has proven to be a great help when debugging and troubleshooting rewrite rules. When you enable Failed Request Tracing and make an HTTP request that you want to trace, IIS creates a trace log file fr NNNNNN .xml located by default at %WINDIR%\inetpub\logs\FailedReqLogFiles\W3SVC N . This xml file references freb.xsl file that is used to render the trace data in a web browser in a human-friendly...(&lt;a href="http://blogs.iis.net/ruslany/archive/2008/10/30/debug-and-troubleshoot-rewrite-rules-easily.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.iis.net/aggbug.aspx?PostID=2713746" width="1" height="1"&gt;</description><category domain="http://blogs.iis.net/ruslany/archive/tags/URLRewrite/default.aspx">URLRewrite</category><category domain="http://blogs.iis.net/ruslany/archive/tags/Tracing/default.aspx">Tracing</category></item><item><title>ASP.NET postbacks and URL rewriting</title><link>http://blogs.iis.net/ruslany/archive/2008/10/23/asp-net-postbacks-and-url-rewriting.aspx</link><pubDate>Thu, 23 Oct 2008 05:04:11 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:2701108</guid><dc:creator>RuslanY Blog</dc:creator><slash:comments>0</slash:comments><description>ASP.NET Web Forms extensively use postback mechanism in order to maintain the state of the server-side controls on the web page. This makes it somewhat tricky to perform URL rewriting for ASP.NET pages. When a server side form control is added to the web page, ASP.NET will render the response with HTML &amp;lt;form&amp;gt; tag that contains an action attribute pointing back to the page where the form control is. This means that if URL rewriting was used for that page, the action attribute will point back to the rewritten URL, not to the URL that was requested from the browser. This will cause the browser to show rewritten URL any time a postback occurs. Let me demonstrate this on an example. Assume you have a very simple web form in a file called default...(&lt;a href="http://blogs.iis.net/ruslany/archive/2008/10/23/asp-net-postbacks-and-url-rewriting.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.iis.net/aggbug.aspx?PostID=2701108" width="1" height="1"&gt;</description><category domain="http://blogs.iis.net/ruslany/archive/tags/Other/default.aspx">Other</category><category domain="http://blogs.iis.net/ruslany/archive/tags/ASPNET/default.aspx">ASPNET</category></item><item><title>Wildcard script mapping and IIS 7 integrated pipeline</title><link>http://blogs.iis.net/ruslany/archive/2008/09/30/wildcard-script-mapping-and-iis-7-integrated-pipeline.aspx</link><pubDate>Wed, 01 Oct 2008 03:30:18 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:2655904</guid><dc:creator>RuslanY Blog</dc:creator><slash:comments>0</slash:comments><description>The big benefit of IIS 7 integrated request processing pipeline is the fact that all the nice and useful ASP.NET features can be used for any type of content on your web site; not just for ASP.NET-specific content. For example, ASP.NET SQL-based membership can be used to protect static files and folders. Also, ASP.NET extensibility API&amp;#8217;s, such as IHttpHandler and IHttpModule can be used to add custom modules and handlers that would be executed even for non-ASP.NET content. IIS 6 did not have this level of integration. ASP.NET was plugged into IIS 6 as an ISAPI extension and by default was configured to handle ONLY requests mapped to that extension - for example any request that ended with &amp;#8220;.aspx&amp;#8221; would be be processed by ASP...(&lt;a href="http://blogs.iis.net/ruslany/archive/2008/09/30/wildcard-script-mapping-and-iis-7-integrated-pipeline.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.iis.net/aggbug.aspx?PostID=2655904" width="1" height="1"&gt;</description><category domain="http://blogs.iis.net/ruslany/archive/tags/Other/default.aspx">Other</category><category domain="http://blogs.iis.net/ruslany/archive/tags/ASPNET/default.aspx">ASPNET</category></item><item><title>Video walkthrough for URL Rewrite Module</title><link>http://blogs.iis.net/ruslany/archive/2008/09/19/video-walkthrough-for-url-rewrite-module.aspx</link><pubDate>Fri, 19 Sep 2008 21:14:40 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:2633789</guid><dc:creator>RuslanY Blog</dc:creator><slash:comments>0</slash:comments><description>Last week I have recorded a video screencast that shows how to use URL Rewrite Module for IIS 7.0 to perform some common URL manipulations tasks. Today this video has been published on IIS.NET - check it out at this location . The video demonstrates how to create rewrite rules to perform the following tasks: Enabling user friendly and search engine friendly URLs for dynamic web pages; Enforcing canonical host names, so that site visitors as well as search engines always use a particular domain name for your web site; Using rewrite maps to define static mappings between requested and rewritten URLs; Blocking unwanted site crawlers by aborting requests based on HTTP user-agent header. In addition, the video shows how to test, troubleshoot and...(&lt;a href="http://blogs.iis.net/ruslany/archive/2008/09/19/video-walkthrough-for-url-rewrite-module.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.iis.net/aggbug.aspx?PostID=2633789" width="1" height="1"&gt;</description><category domain="http://blogs.iis.net/ruslany/archive/tags/Uncategorized/default.aspx">Uncategorized</category></item><item><title>URL Rewrite Module - Go Live release</title><link>http://blogs.iis.net/ruslany/archive/2008/09/11/url-rewrite-module-go-live-release.aspx</link><pubDate>Thu, 11 Sep 2008 17:27:15 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:2615989</guid><dc:creator>RuslanY Blog</dc:creator><slash:comments>0</slash:comments><description>Today IIS team has made the Go Live release of URL Rewrite Module for IIS 7.0 available for download. This release contains significant functionality and performance improvements and it is believed to have a quality level suitable for production deployments. Download the Go Live release of the module today! Microsoft URL Rewrite Module for IIS 7.0 Go Live (x86) Microsoft URL Rewrite Module for IIS 7.0 Go Live (x64) Note that the installer for URL Rewrite Module includes the FastCGI update for IIS 7.0 . If this update has not been yet installed on your machine it will be installed together with URL Rewrite Module. New Features since CTP release Here are the features that are new since CTP release (for a complete list of features and changes since...(&lt;a href="http://blogs.iis.net/ruslany/archive/2008/09/11/url-rewrite-module-go-live-release.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.iis.net/aggbug.aspx?PostID=2615989" width="1" height="1"&gt;</description><category domain="http://blogs.iis.net/ruslany/archive/tags/IIS+News+Item/default.aspx">IIS News Item</category><category domain="http://blogs.iis.net/ruslany/archive/tags/URLRewrite/default.aspx">URLRewrite</category></item><item><title>ASP.NET Routing, Request Filtering, URL Rewriting</title><link>http://blogs.iis.net/ruslany/archive/2008/09/04/asp-net-routing-request-filtering-url-rewriting.aspx</link><pubDate>Thu, 04 Sep 2008 18:28:30 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:2611006</guid><dc:creator>RuslanY Blog</dc:creator><slash:comments>0</slash:comments><description>Today I have published two new articles on http://learn.iis.net . The articles are intended to explain the differences between various URL manipulation technologies available in IIS 7.0 and to provide help with choosing of the technology best suited for a particular usage scenario. Here is the short summary of the articles: IIS 7.0 URL Rewriting and ASP.NET Routing - with the release of URL-rewrite module for IIS 7.0 and the inclusion of ASP.NET routing into the .NET Framework 3.5 SP1, there have been a lot of questions from ASP.NET developers about how these two features relate to each other and when to use each. This article describes the differences between these two technologies and provides guidance for Web developers on when to use IIS...(&lt;a href="http://blogs.iis.net/ruslany/archive/2008/09/04/asp-net-routing-request-filtering-url-rewriting.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.iis.net/aggbug.aspx?PostID=2611006" width="1" height="1"&gt;</description><category domain="http://blogs.iis.net/ruslany/archive/tags/URLRewrite/default.aspx">URLRewrite</category></item><item><title>Update for IIS 7.0 FastCGI module</title><link>http://blogs.iis.net/ruslany/archive/2008/08/27/update-for-iis-7-0-fastcgi-module.aspx</link><pubDate>Wed, 27 Aug 2008 02:10:00 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:2611007</guid><dc:creator>RuslanY Blog</dc:creator><slash:comments>0</slash:comments><description>IIS team has recently released an update for IIS 7.0 FastCGI module that fixes compatibility problems with several popular PHP applications. In particular, the update changes the behavior of FastCGI module in the following ways: REQUEST_URI server variable set by FastCGI module now includes query string and path info. Previously, lack of the query string in this server variable caused the popular CMS application Drupal to not work with FastCGI on IIS 7.0 REQUEST_URI server variable now contains the originally requested URL path before any URL rewriting was performed. Prior to this fix, the server variable used to contain a final rewritten URL, which caused problems when using URL rewriting to enable “pretty permalinks” for popular blog engine...(&lt;a href="http://blogs.iis.net/ruslany/archive/2008/08/27/update-for-iis-7-0-fastcgi-module.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.iis.net/aggbug.aspx?PostID=2611007" width="1" height="1"&gt;</description><category domain="http://blogs.iis.net/ruslany/archive/tags/PHP/default.aspx">PHP</category><category domain="http://blogs.iis.net/ruslany/archive/tags/FastCGI/default.aspx">FastCGI</category><category domain="http://blogs.iis.net/ruslany/archive/tags/Wordpress/default.aspx">Wordpress</category><category domain="http://blogs.iis.net/ruslany/archive/tags/Drupal/default.aspx">Drupal</category><category domain="http://blogs.iis.net/ruslany/archive/tags/IIS+News+Item/default.aspx">IIS News Item</category></item><item><title>Ruby on Rails in IIS 7.0 with URL Rewriter</title><link>http://blogs.iis.net/ruslany/archive/2008/08/07/ruby-on-rails-in-iis-7-0-with-url-rewriter.aspx</link><pubDate>Thu, 07 Aug 2008 17:57:15 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:2611008</guid><dc:creator>RuslanY Blog</dc:creator><slash:comments>0</slash:comments><description>If you ever tried to set up Ruby on Rails (RoR) on IIS 7.0 with FastCGI you have probably noticed that the process is not very straightforward. There are a few workarounds that need to be applied in order for RoR to function correctly. In particular, handling of static files in your web application can be tricky on IIS 7.0. The problem is that RoR uses clean URL&amp;#8217;s that look similar to this: http://mysite.com/home/about . In order for RoR to be invoked for this kind of URL&amp;#8217;s it is necessary to create a &amp;#8220;catch all&amp;#8221; handler mapping in IIS (that is a handler mapping with path attribute set to &amp;#8220; * &amp;#8220;). When you create such a handler mapping it will cause requests for static files to be routed to RoR, which will...(&lt;a href="http://blogs.iis.net/ruslany/archive/2008/08/07/ruby-on-rails-in-iis-7-0-with-url-rewriter.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.iis.net/aggbug.aspx?PostID=2611008" width="1" height="1"&gt;</description><category domain="http://blogs.iis.net/ruslany/archive/tags/FastCGI/default.aspx">FastCGI</category><category domain="http://blogs.iis.net/ruslany/archive/tags/URLRewrite/default.aspx">URLRewrite</category><category domain="http://blogs.iis.net/ruslany/archive/tags/RubyOnRails/default.aspx">RubyOnRails</category></item><item><title>Scripting URL rewrite module configuration</title><link>http://blogs.iis.net/ruslany/archive/2008/07/28/scripting-url-rewrite-module-configuration.aspx</link><pubDate>Mon, 28 Jul 2008 04:18:21 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:2611009</guid><dc:creator>RuslanY Blog</dc:creator><slash:comments>0</slash:comments><description>URL rewrite module fully utilizes extensibility of IIS 7.0 configuration system. The rewrite rules are stored in applicationHost.config and web.config files in XML format. This provides a huge benefit of being able to use rich set of IIS 7.0 management tools and API&amp;#8217;s for managing and scripting URL rewriter configuration. For example, you can automate any configuration task, including creating, editing and deleting of rewrite rules, by: writing .NET code that uses Microsoft.Web.Administration API&amp;#8217;s; writing JavaScript code; using IIS command line tool appcmd.exe ; using PowerShell provider . The Configuration Editor , included in the Administration Pack for IIS 7.0 , greatly simplifies the process of generating scripts for automating...(&lt;a href="http://blogs.iis.net/ruslany/archive/2008/07/28/scripting-url-rewrite-module-configuration.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.iis.net/aggbug.aspx?PostID=2611009" width="1" height="1"&gt;</description><category domain="http://blogs.iis.net/ruslany/archive/tags/URLRewrite/default.aspx">URLRewrite</category></item><item><title>IIS.NET uses URL rewrite module</title><link>http://blogs.iis.net/ruslany/archive/2008/07/18/iis-net-uses-url-rewrite-module.aspx</link><pubDate>Fri, 18 Jul 2008 18:46:54 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:2611010</guid><dc:creator>RuslanY Blog</dc:creator><slash:comments>0</slash:comments><description>IIS.NET team has been very proactive in helping us out with testing of URL rewrite module . In fact, they even agreed to deploy the latest build of the module on the production server that hosts http://www.iis.net . This kind of real-life deployments really helps us validate the features and functionality of the module. And being able to do this validation so early in release cycle gives us a good opportunity to adjust the feature set, re-consider some of the design decisions, or just find some very good bugs. IIS.NET has URL rewriting requirements, which are typical for large content management systems. The articles on the site are often moved or updated and the old links should continue to work. Or there is a need to have a nice URL (for example...(&lt;a href="http://blogs.iis.net/ruslany/archive/2008/07/18/iis-net-uses-url-rewrite-module.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.iis.net/aggbug.aspx?PostID=2611010" width="1" height="1"&gt;</description><category domain="http://blogs.iis.net/ruslany/archive/tags/URLRewrite/default.aspx">URLRewrite</category></item><item><title>Per-site PHP configuration with IIS FastCGI</title><link>http://blogs.iis.net/ruslany/archive/2008/07/12/per-site-php-configuration-with-iis-fastcgi.aspx</link><pubDate>Sat, 12 Jul 2008 08:03:32 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:2611003</guid><dc:creator>RuslanY Blog</dc:creator><slash:comments>0</slash:comments><description>There have been a few questions on IIS.NET PHP forum regarding enabling per-site PHP configuration. This is a common requirement when running PHP applications in shared hosting environment, because each PHP application may require a different set of PHP settings. Shared hosting providers often want to provide their customers with an option of controlling PHP configuration if necessary. Until recently, it was thought that per-site PHP configuration was only possible when running PHP on Apache in *nix based OS. However, with FastCGI module it is possible to enable this for PHP applications hosted on IIS 6.0 and IIS 7.0. The development team at GoDaddy.com has researched and validated several options for enabling per-site PHP configuration on Windows...(&lt;a href="http://blogs.iis.net/ruslany/archive/2008/07/12/per-site-php-configuration-with-iis-fastcgi.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.iis.net/aggbug.aspx?PostID=2611003" width="1" height="1"&gt;</description><category domain="http://blogs.iis.net/ruslany/archive/tags/PHP/default.aspx">PHP</category><category domain="http://blogs.iis.net/ruslany/archive/tags/FastCGI/default.aspx">FastCGI</category></item><item><title>Introduction</title><link>http://blogs.iis.net/ruslany/archive/2008/07/11/introduction.aspx</link><pubDate>Fri, 11 Jul 2008 05:29:11 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:2611002</guid><dc:creator>RuslanY Blog</dc:creator><slash:comments>0</slash:comments><description>My name is Ruslan Yakushev. I am a program manager on IIS team, working on some of the very interesting projects that are being developed in the team right now. I have joined the team about a year ago, and was thinking about starting a blog for a while now. The primary work responsibilities kept me busy, so I have been postponing blog idea for a while. Every time I needed to make an announcement or an update on IIS community site, I asked some of my colleagues on the team to blog my content. Finally, I figured that I should probably start my own blog, so I could have all the freedom of publishing my own content any time I want. Being a technical program manager on the team, I like to use (in other words - &amp;#8220;dogfood&amp;#8221;) the products...(&lt;a href="http://blogs.iis.net/ruslany/archive/2008/07/11/introduction.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.iis.net/aggbug.aspx?PostID=2611002" width="1" height="1"&gt;</description><category domain="http://blogs.iis.net/ruslany/archive/tags/Other/default.aspx">Other</category></item></channel></rss>