Over the past several years I’ve found myself running into the same problem over and over so I thought I’d blog the solution so at least I don’t waste time figuring it out again.  So, when do you need this?  The answer for me is that I want to be able reference a web site without having to expose the underlying site structure.  For example, on the home page of my business, I want people to be able to type http://73rdstreet.com/Home and be taken to http://www.73rdstreet.com/HomeSite/Home.aspx.

The Symptom

You may see errors that say something like:

Server Error in Application … HTTP Error 404.0 – Not Found

The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.

MapRequestHandler StaticFile

And the screen may show something like this.

If this happens, read on.

Theory

The first thing to understand is that IIS by default will pass to the asp.net process only the requests that have a certain file extension.  That is, aspx,ashx,etc.  Basically, only file extensions that have a handler defined for them to be processed by.  Other URL’s that don’t meet the criteria are not passed to IIS.  This includes no file extension at all.  There is a good reason for this.  One, it makes processing of things like images (jpg’s, gif’s, etc.) faster because they do not every have to be processed through the asp.net worker process.  Secondly, it lowers the exposure of the asp.net worker process so that it is less likely to be compromised.

So, the first thing that has to be done is to tell IIS to pass all requests through using something called Wild Card Mapping.  Then, once this is done, the request comes through to the asp.net worker process regardless of what it is.  As we know, the place that we would have to process this is an HttpModule.  The reason is that since it’s not a page yet, we have no idea what to do with it.  Basically modules let you tap into the request at different stages.  To do the rewrite from ../Home to ../HomeSite/Home.aspx we want to tap into the Application_BeginRequest event.  The Context.RewritePath method is called at that point to force a new path based on what we want (hopefully not hard coded).

After the ReWritePath is set, the page is processed as if is going to the correct page.

How To Set Wild Card Mapping in IIS6

To Set Wild Care Mapping in IIS6 you need to do the following.

Run inetmgr and navigate to the Properties page of the website you want to set.

Then, from the properties page, click the Configuration button as shown below.

Then, press the insert button on the configuration screen and see the following screen and then click on the insert button.

Now, insert your asp.net isapi dll.  On my system, the file is here:  C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll.  Make sure to uncheck the box "Verify that file exists".

That’s it! Now, all requests will be processed through you asp.net pipeline so you will be able to intercept anything on the URL you want.  Be careful though, you may get more than you ask for!

How To Set Wildcard Mapping in IIS7

In IIS7 things are a little different.  First thing you need to do is unlock the config section "handlers". You do this by bring up a DOS prompt and entering the command:

C:\Windows\System32\inetsrv>appcmd.exe unlock config /section:system.webserver/handlers

Then, you can set your wildcard handler in your web.config file as follows.

Now, the default handlers will be executed in your web.config file, and of course, all the defaults for that are in the chain of files that inherits from.  For more details on that, see this FAQ: Configuration Files FAQs (web.config, machine.config…).

You may need to add the wildcard mapper handler to your web.config.  To do this, you would put the following in your web.config

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <system.webServer>
        <handlers>
            <add name="WildCard" path="*" verb="*" type="sampletype" resourceType="Unspecified" />
        </handlers>
    </system.webServer>
</configuration>

Now, you should be set. See the next section for a good method for actually doing the remapping, which is why we went down this path in the first place.

Implementing a URL ReWriter for Mapping ../Home to ../HomeSite/Home.aspx

So, as discussed in the theory section above, you could write your own code to map what you want to where you want it.  You could put in your global.asax some code for the Application_BeginRequest and make a big case statement for everything you want to do.  Well, as we know, that would give your code a bad smell and we don’t want that because soon, you will find yourself using cut and paste and other problematic crutches.

So, to avoid all that, and do what Scott Guthrie suggests, use the open source package UrlRewriter.NET.  It’s light-weight and configurable through a small section in your web.config. Before putting in the what to do, here are the steps to make UrlRewriter work in a very simple way (the way I use it on my company home page.

In your <System.web> of your web.config place a definition for a new config section where you will put your rewrites

<configuration>

    <configSections>

      <section name="rewriter" requirePermission="false" 

        type="Intelligencia.UrlRewriter.Configuration.RewriterConfigurationSectionHandler, Intelligencia.UrlRewriter"/>

Then, put the module that actually does the work of the rewrite as described in the theory section above

<system.web>

   <httpModules>

     <add name="UrlRewriter" 

           type="Intelligencia.UrlRewriter.RewriterHttpModule, Intelligencia.UrlRewriter" />

     </httpModules>

       ..

Then, further down in your web.config put

<system.webServer>

  <validation validateIntegratedModeConfiguration="false"/>

  <modules>

    <add name="UrlRewriter"

         type="Intelligencia.U

<rewriter>

  <rewrite url="~/Home" to="~/pages/Home.aspx"/>

</rewriter>

That’s it!  You are done.  Hope this helps, or at least helps me the next time I’m searching for the same problem (for the 4th time at least).

References:

• http://devtalk.dk/2007/03/19/Wildcard+Mapping+And+URL+Rewriting+On+IIS7.aspx
• http://weblogs.asp.net/scottgu/archive/2007/02/26/tip-trick-url-rewriting-with-asp-net.aspx
• http://urlrewriter.net/
• http://forums.asp.net/t/1240344.aspx
• http://professionalaspnet.com/archive/2007/07/27/Configure-IIS-for-Wildcard-Extensions-in-ASP.NET.aspx
• http://professionalaspnet.com/archive/2007/07/27/Create-an-HttpModule-to-Process-Wildcard-Extension-Mapping-in-ASP.NET.aspx

Turns out when I added the web server in vista, I forgot to check the Static Content checkbox under World Wide Web Services / Common Http Features.

Hope this finds you if you are having the same problem.

This issue has come up several times for me.  That is, you have an image  url you want to display in your silverlight .net 1.1 application that comes from  some foreign server.  That is, you want this to work:  (and of course
it does not).

The Problem

Even though, you can do this:

There seems to be a subtle difference having to do with cross domain security  that I just don’t get but since it’s there, we have to deal with it.

The Solution

So first, why do you even care.  Why not just do the one that works?  Well, the answer is that you want to be able to deal with what happens while an image is being downloaded.  My particular problem has to do with what happens when you bring up a picture in a modal dialog type thing.  That is, you click on a small thumbnail, and a larger ones comes up.  In my case, I’m getting the image url from a web service so I don’t have the luxury of opening it locally.  I have to use a foreign (remote) url.  And, the reason I don’t want to open it by simply setting the source tag is that I’m
reusing a control.  This means that I’m simply hiding it and unhiding it. If I just set the source and unhide it, the wrong image comes up.  That is, the one from the previous request. Then, a few seconds later, the correct image
comes up.  Bad.

We really want to use the Downloader object.  A very cool control, but not if it doesn’t work cross domain IMHO.

The work around for this is to write a http handler that runs in your local asp.net project that you pass the url you want to display. Then, that web service turns around, calls the cross domain server, gets the image and returns it to your Downloader object.  Simple in concept, but the devil is in the details.  How, for example to you pass a url (that may include all kinds of stuff like &’s to a local web service.  The answer is encode it!  Then decode it at the web service.  I’m sure you all can whip that up quickly, but since I did already, why bother.  I’m going to paste the code below with brief explanations to help.  Here goes:

The Silverlight UserControl That Calls the web service

The way I did the code in the silverlight control is to encode the real URL I want.  That is the one cross domain.  I think build a URL that calls my local web service passing the parameter encoded as a base64 value as one of
the url parameters.  I’m using a property in my usercontrol to set this value just because that’s kind of convenient.  Here is what the code looks like:

Just to give you a hint of what the might look like, in my case, this is what it is:

http://localhost:49803/WebService/DisplayImage.ashx?URL=aHR0cDov…NDE0NzU2LkpQRw==&Width=400

(I put a bunch of …’s in the middle, but it was longer than that originally)

Silverlight is kind of limited on conversion functions so I had to write this little one called EncodeTo64 which is pasted below.  I’m sure there are better ways to do it, but this one works.

And, don’t forget that you need to have the completed event code in your silverlight side to handle setting the source tag when the image is fully downloaded.  Here is that function.

The Http Handler (DisplayImage.ashx file)

To make all this come to live, you need an http handler that will make the call to the cross domain server.  Below is that code.  I added an extra parameter for width so that if you know the image you need is smaller than the one across the internet, you can just get downloaded what you need.  Here is the code for the handler:

Conclusion

I’m guessing that this problem will go away in the next alpha or beta release of Silverlight .net.  In the mean time, this works very well for me and hopefully will for you also.  I don’t have this in a good sample application and really just wanted to get it posted because I know others were having the same problems.  If someone goes through and makes a good demo of this, please post a comment with the code for others to download.

Thanks for reading, and best of luck with your Silverlight Development!