Hi Greg,
I'm not sure what you are asking. ISAPI filters are not invoked at all
based on file extension. They are invoked by event notifications on the
server.
If you do have a filter, then it will get notified any time any of the
events for which it's registered occurs, regardless of the URL. If your
filter gets notified, and it does not want to process the notification for
any particular reason (in your case, due to the file extension in the URL),
then it should just return SF_STATUS_REQ_NEXT_NOTIFICATION from
HttpFilterProc.
One other note: You say that "everything else goes to the filter." Are you
aware that the ISAPI filter architecture is not intended to handle requests?
If you are trying to serve content for everything except the below URLs,
then you should write your filter such that it modifies the URL in
SF_NOTIFY_PREPROC_HEADERS so that the request goes to an ISAPI extension
(ISAPI extensions are specifically intended to handle requests.)
If you would like any further information about this or any other ISAPI
issue, please feel free to post to
microsoft.public.platformsdk.internet.server.isapi-dev, which exists for
this purpose.
Thank you,
-Wade A. Hilmo,
-Microsoft
"greg" <sender.DeleteThis@nospam.com> wrote in message
news:eONsCXCwDHA.2540@TK2MSFTNGP09.phx.gbl...
> Hello,
> I have a quick question about iis and isapi filters.
> Is there a way to set up IIS kinda the opposite of how you are suppost to
> set up isapi filters?
> meaning, I do not want to set up my filter to * or .xyz, or whatever.
> I would like to say, iis takes html, htm, css, bmp and everything else
goes
> to the filter.
>
> Some of our components do not have an extension, such as component/main.
> If we set up the filter for * then the filter seems to get overwhelmed.
>
> thanks in advance
>
>
>
><!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: isapi filter question