Manual:Short URL/IIS7

Generic Tutorial on IIS Rewrite Module
The following tutorial offers a number of articles to describe the IIS Rewrite module: Using URL Rewrite Module. IIS.net also has a tutorial on setting up MediaWiki on IIS, including an overview of "Enabling clean URLs with URL Rewrite Module": MediaWiki on IIS

Using the IIS URL Rewrite Module with MediaWiki
The following steps were performed to successfully integrate the IIS URL Rewrite Module with the Short URL capability offered by MediaWiki using Windows 7 or 2008 Small Business Server and IIS 7.0:


 * 1) Install the IIS URL Rewrite Module 2.0:
 * 2) Download appropriate 32bit or 64bit IIS Rewrite Module from Microsoft:
 * 3) * (x86): 32bit Rewrite Module from Microsoft (Version 2: download)
 * 4) * (x64): 64bit Rewrite Module from Microsoft (Version 2: download)
 * 5) Install on the host server by running the downloaded .msi file
 * 6) Create a rewrite rule:
 * 7) Open the Internet Information Services (IIS) Manager
 * 8) Select the site that contains the MediaWiki installation
 * 9) Select "URL Rewrite" within the IIS Area group features
 * 10) Click "Add Rules..." (on the right-hand "Actions" panel)
 * 11) Select "Blank Rule" and click "OK" (displays the Edit Rule pane)
 * 12) Enter a unique name for the rule (e.g. WikiShortURLStd)
 * 13) Set the "Requested URL" drop down to "Matches the pattern"
 * 14) Set the "Using" drop down to "Regular Expressions"
 * 15) Enter ^wiki/(.*)$ in the "Pattern" field -- no leading slash (i.e. "wiki/" not "/wiki/"!)
 * 16) Don't add any conditions
 * 17) Set the "Action Type" drop down to "Rewrite"
 * 18) Enter w/index.php?title={R:1} in the "Rewrite URL" field
 * 19) * (Where w is the http document path of your MediaWiki installation (e.g. www.example.com/w))
 * 20) Leave the "Append query string" check box as checked
 * 21) Press Apply (on the right-hand "Actions" panel)
 * 22) Edit the appropriate path configurations in your LocalSettings.php file:
 * $wgScriptPath = "/w"; The directory under your document root where MediaWiki is installed
 * $wgArticlePath = "/wiki/$1"; This is the rewritten URL
 * $wgUsePathInfo = true;

Additional Info
For those using the above settings and experiencing problems with special pages (or any with the ':' (colon) character in them) try using the following in the "Rewrite URL" field "w/index.php?title={UrlEncode:{R:1}}"

If your wiki is installed in the root of your website (www.example.com/index.php?title=...), w is nothing. Use "/index.php?title={R:1}" in the "Rewrite URL" field.

Subdomain Wiki Uses
For those interested in using subdomains with their account, you must create a different regular expression within IIS. Instead of using the ^wiki/(.*)$ pattern match. You must use ^[a-zA-Z_0-9/:\-]*$ or something extremely close to this. CSS wasn't working with the above method, so switching to this regular expression helped greatly.

GoDaddy IIS7 Hosting Notes
Since GoDaddy has shared hosting of IIS7, you will not be able to use the IIS management console to enter the URL rewrite parameters. Fortunately GoDaddy has installed the URL rewrite module already, so all that is left for you to do is to upload a web.config file to your wiki root folder.

The below example is the entire contents from the web.config used successfully to mimic the effect detailed by the ".htaccess" file mentioned in the main Short URL article:

Alternative
The code below has been used successfully on IIS7 on Windows Server 2008, with PHP 5.2.1.2 and MediaWiki 1.15.1 using the URL Rewrite Module, Friendly URL writer: Note: Make sure you either switch to source view before copying the code into your web.config file. The QUERY_STRING pattern above contains an ampersand, which will not get copied correctly unless you switch to source view. In XML string literals, an ampersand is properly represented as the ampersand character followed immediately by the text "amp;" (not including the quotes). If you do not switch to source view and you copy the above code as is, IIS 7 will generate a 500.19 error with the message that the configuration data is invalid due to malformed XML.