Skip to main content

URL Rewriting

Recently it came to my attention that google and other major search engines were no longer indexing querystrings. I'm not sure when the switch took place but on a number of sites I maintain the majority of the content is no longer indexed.

Enter URL Rewriting which allows us to convert:


This is extremely commonplace in the Apache world, but how do we accomplish it within IIS?

Today I downloaded Helicon's ISAPI_Rewrite 2.11 Lite. It's free and best of all it works off regular expressions.

Installation and Configuration
1.) Download ISAPI_Rewrite
2.) Install
3.) Open the global httpd.ini file
Start > Programs > Helicon > ISAPI_Rewrite > httpd.ini
4.) Add a rule to process querystrings, in this example we'll loop through the querystring of all files ending in .aspx

# Repath .aspx files
RewriteRule (.*?\.aspx)(\?[^/]*)?/([^/]*)/([^/]*)(.*) $1(?2$2&:\?)$3=$4$5 [NS,I]

This will turn:


Extra points if you've actually used a McLeod (or at least know what one is).

The Lite version of ISAPI_Rewrite only works at the global level, and cannot be configured to work differently in each virtual directory. So far it is working really well, and I may be buying a full version in the near future.



Popular posts from this blog

Simple HTTP Redirect with Querystring in IIS7

HTTP Redirect seems simple enough. Always was in IIS6 and in IIS7 there's even a button labeled HTTP Redirect that promises relative redirects.  It looks like it'll be as easy Apache finally.  That is until you try to redirect a querystring.  Then everything bombs.

Turns out it still is relatively easy, except you have to know that Microsoft changed $S$Q to $V$Q. Why? $Ss and $Gs I suspect.

And How.
In our example we'll redirect all pages under to
Pick the virtual directory you want to redirect. e.g. Click HTTP Redirect under IIS in the IIS management console.In the HTTP Redirect Dialog:
Check Redirect requests to this destinationEnter your new path ending with $V$Q.  e.g.$V$QCounter-intuitively check Redirect all request to exact destination (instead of relative destination)Choose the appropriate Status Code (Permanent or Temporary)Apply Changes and Test

Resultant table not allowed to have more than one AutoNumber field

Ever get this error on a create table or insert query? The work around is quite simple. Cast the autonumber as an integer. In query design view change your field definition for one of your autonumbers to read:
XID: CInt([ID])
Or in SQL View:
(Ran into this error message again this morning and it reminded me I should share the workaround.)

Serving up KML in IIS 6

To serve up KML in IIS 6, you have to add a few MIME Types. The easiest way to do this is to apply new MIME Type settings globally by changing the properties on your server's "Web Sites" folder in IIS.

Google Earth reads KML and KMZ files. The MIME type for KML files is

* application/

The MIME type for KMZ files is

* application/

Source: Google KML Tutorial

To add a MIME type to a Web site or directory

1. In IIS Manager, right-click the Web site or Web site directory for which you want to add a MIME type, and click Properties.

2. Click the HTTP Headers tab.

3. Click MIME Types.

4. Click New.

5. In the Extension box, type the file name extension.

6. In the MIME type box, type a valid MIME type. If you define a MIME type that has already been defined at a higher level, you are prompted to select the level where the MIME type should reside.

To create a MIME type for an undefined MIME type, type an asterisk (*) in the Extension box, an…