Re: 404 handler mkicks in before ISAPI filter
From: David Wang [Msft] (someone_at_online.microsoft.com)
Date: 03/08/04
- Next message: Jolene: "Domain name issues"
- Previous message: David Wang [Msft]: "Re: Error starting IIS5.0 (To Bernard Cheah or anyone who know what to do)"
- In reply to: Yoram Ayalon: "Re: 404 handler mkicks in before ISAPI filter"
- Next in thread: Yoram Ayalon: "Re: 404 handler mkicks in before ISAPI filter"
- Reply: Yoram Ayalon: "Re: 404 handler mkicks in before ISAPI filter"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 8 Mar 2004 09:36:05 -0800
Please do not multi-post.
This looks to be a bug in the ISAPI Filter you are using and has nothing to
do with IIS.
If properly written, an ISAPI Filter WILL be able to do all those URL
transformations before the 404 Handler is even invoked.
You want it to do this:
www.mydomainname.com/param1/value1 --> www.mydomainname.com?param1=value1
But it may be doing this (I have no idea how the ISAPI Filter is choosing to
rewrite URLs):
www.mydomainname.com/param1/value1 --> www.mydomainname.com/param1?value1=
Which would probably result in a legitimate 404 since /param1 does not
exist.
-- //David IIS This posting is provided "AS IS" with no warranties, and confers no rights. // "Yoram Ayalon" <yoram.ayalon@structuredweb.com> wrote in message news:1f08621e.0403061122.60857944@posting.google.com... 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: Jolene: "Domain name issues"
- Previous message: David Wang [Msft]: "Re: Error starting IIS5.0 (To Bernard Cheah or anyone who know what to do)"
- In reply to: Yoram Ayalon: "Re: 404 handler mkicks in before ISAPI filter"
- Next in thread: Yoram Ayalon: "Re: 404 handler mkicks in before ISAPI filter"
- Reply: Yoram Ayalon: "Re: 404 handler mkicks in before ISAPI filter"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|