Re: 404 handler mkicks in before ISAPI filter

From: Yoram Ayalon (yoram.ayalon_at_structuredweb.com)
Date: 03/06/04

  • Next message: Paul: "Re: cs-host, host header and destination" 
    Date: 6 Mar 2004 11:22:54 -0800

    Tim,

    thanks for the info but I don't think this is relevant. I am not
    creating any virtual directories here, its simply a case of the IIS
    trying to resolve the URL to a physical file or folder BEFORE the
    ISAPI filter has a chance to convert the slashes to a valid query
    string.

    "Tim Heuer" <tim@nospam.timheuer.com> wrote in message news:<etvoowwAEHA.684@tk2msftngp13.phx.gbl>...
    > http://support.microsoft.com/?kbid=275601

    > "Yoram Ayalon" <yoram.ayalon@structuredweb.com> wrote in message
    > news:1f08621e.0403051420.57e4e7e9@posting.google.com...
    > >I installed an ISAPI filter that translates "forward slashes" at the
    > > end of a URL to a query string format, ex:
    > > www.mydomainname.com/page1.asp/param1/value1
    > > will be translated to: www.mydomainname.com/page1.asp?param1=value1
    > >
    > > however, if the incoming URL is
    > > www.mydomainname.com/param1/value1
    > > then the 404 handler for the default web site kicks in BEFORE the
    > > isapi filter has a chance to translate.
    > > page1.asp is the default page for the default web site, if the
    > > incoming URL is www.mydomainname.com?param1=value1 it works just fine.
    > >
    > > How can I fix this?
    > >
    > > IIS version 5.0 on win2K
    > >
    > > NOTE: I need the 404 handler on the default web site, since I need to
    > > catch obsolete folder names. I tried to return to the default handling
    > > but still it kicks in before the ISAPI filter.

  • Next message: Paul: "Re: cs-host, host header and destination"
    Loading