IIS 5.1, path based HttpHandler does not work. Can I fix it with IIRF?

I have a reverse proxy written in C # / ASP.NET. After adding wildcard mapping in IIS6, it works fine. My problem is that I have to make this application compatible with Windows XP and IIS 5.1. The first time I try to add a wildcard file displayed in aspnet_isapi.dll does not work. I've also tried using the file extension to no avail.

My next path is to explore with the Ionic Isapi Rewrite Filter (IIRF) to redirect requests to my Asp.Net application. Has anyone used it for this purpose? I think I still need to change the way my reverse proxy works.

Now, through the process, I create a connection, so the user sees:

http://example.com/remotesite/34x904/home.htm

      

        
        
        
      

    

and I have HttpHandler mapped to remotesite / virtual path

<add verb="*" path="/remotesite/*" validate="false" type="Proxy.Core.HttpHandler,Proxy.Core"/>

      

        
        
        
      

    

and the backend HttpWebRequest will end up using the URI like:

http://10.1.1.21/home.htm

      

        
        
        
      

    

In IIS 5, I have trine mapping by file extension, but I still get Paged cannot be mapped.

<add verb="*" path="test.proxy" validate="false" 
type="Proxy.Core.HttpHandler,Proxy.Core"/>
 <add verb="*" path="/test.proxy/*" validate="false" 
type="Proxy.Core.HttpHandler,Proxy.Core"/>