« Previous Next »

Thread: RTW release of URL Rewrite Module for IIS 7.0

Last post 11-10-2008 5:20 PM by ruslany. 0 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (1 items)

Sort Posts:

  • 11-10-2008, 5:20 PM

    • ruslany
    • Top 25 Contributor
    • Joined on 07-01-2007, 3:38 PM
    • Redmond, WA
    • Posts 660

    RTW release of URL Rewrite Module for IIS 7.0

    Locked Reply Contact

    Today we are releasing the URL Rewrite Module for IIS 7.0 Release To Web (RTW). 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.

    New Features since Go Live release

    Here are the features that are new since Go Live release (for a complete list of features refer to this article):

    • String manipulation functions. Built-in string manipulation functions can be used to convert URLs to lowercase and to perform URL encoding and decoding.

    • UNENCODED_URL server variable. This server can be used to get the raw URL path as it was requested by web client. If the requested URL contained any URL encoded characters, those will not be decoded.

    ASP.NET updates

    The URL rewrite module installer package includes an ASP.NET update that fixes ASP.NET bugs specific to URL rewriting. In particular, the update contains fixes for the following bugs:

    1. ~ operator in ASP.NET Web server control is resolved incorrectly when using URL rewriting
    2. ASP.NET SiteMap.CurrentNode property returns null when sitemap contains virtual URLs

    For more details about these and other ASP.NET issues related to URL rewriting refer to the article "URL rewriting for ASP.NET Web Forms".

    Changes since Go Live release

    The following additions, changes and important bug fixes have been made to URL rewrite module since Go Live release:

    1. Added string manipulation functions UrlEncode and UrlDecode.
    2. Provided access to a raw original URL via server variable UNENCODED_URL. This server variable now contains the raw encoded URL exactly as it was requested by web browser.
    3. Added UI for configuring rewrite rules for Application Request Routing.
    4. Added support for in-place upgrade from Go Live release of URL rewrite module.
    5. Added functionality to clean up the internal cache to avoid excessive usage of memory when caching rewrite rules.
    6. Fixed a bug related to rewriting of URLs that contain non-ASCII characters.
    7. Fixed a bug in regular expression engine that caused character ranges to be evaluated incorrectly for case insensitive patterns.
    8. Fixed bugs in internal rules caching logic.
    9. Included an update for IIS FastCGI module into the installer package.
    10. Included an update for System.Web.dll into the installer package.
    11. Included an update for IIS SetUri function into the installer package.

    Known Issues

    1. Digest authentication cannot be used with URL rewrite module.
    2. ASP.NET Forms Authentication uses rewritten URL for redirection. For example, if requested URL is "/article.htm" and URL rewrite module rewrites the URL to "/article.aspx", which is protected by Forms Authentication, then ASP.NET will redirect to "/login.aspx?ReturnUrl=%2Farticle.aspx".
    3. Auto-detect mode in ASP.NET Forms Authentication uses rewritten URL for redirection. For example, if requested URL is "/article.htm" and URL rewrite module rewrites the URL to "/article.aspx", which is protected by Forms Authentication, then ASP.NET will redirect to "/article.aspx?AspxAutoDetectCookieSupport=1".
    4. UseUri mode in ASP.NET Forms Authentication uses rewritten URL for redirection. For example, if requested URL is "/article.htm" and URL rewrite module rewrites the URL to "/article.aspx", which is protected by Forms Authentication, then ASP.NET will redirect to "/(S(vy2ebt45imfkmjjwboow3l55 ))/article.aspx".
    5. ASP.NET rewrites back to the original URL when using URI-based authentication or cookie-less session state. For example, when request is made to "/(S(vy2ebt45imfkmjjwboow3l55 ))/article.htm" and URL rewrite module rewrites "/article.htm" to "/article.aspx", then ASP.NET will rewrite the URL back to "/article.htm", which may result in a "404 - File Not Found" error.
    6. IIS DefaultDocument module may redirect to rewritten URL when URL rewrite module rewrites to a folder. For example, if substitution URL in rewrite rule is "/folder1/folder2" and these folders exist on file system and have default document configured, then DefaultDocument module will redirect web client to "/folder1/folder2/", thus exposing rewritten URL. To prevent this from happening, use "/" at the end of the substitution URL when rewriting to a folder, e.g. "/folder1/folder2/"

    More information

    New and updated walkthroughs: http://learn.iis.net/page.aspx/460/using-url-rewrite-module/

    Updated configuration reference: http://learn.iis.net/page.aspx/465/url-rewrite-module-configuration-reference/

    Using URL rewrite module with ASP.NET web forms: http://learn.iis.net/page.aspx/517/url-rewriting-for-aspnet-web-forms/

    Extending the URL Rewrite module user interface with custom rule templates: http://learn.iis.net/page.aspx/519/developing-rule-template-for-url-rewrite-module/

    http://ruslany.net
Page 1 of 1 (1 items)
Microsoft Communities