It sounds like your falling foul of the * mapping in your application and
IIS is therefore not processing the unknown path request via the
aspnet_isapi.dll. In theory IIS does not know what to process as it works
on the principle of file extensions. You can solve it with a very small
iHTTPModule to intercept requests to your web application.
In your module begin_request event (might need to check this event) check
the request path contains an extension, if not deal with it by giving it one
that IIS will recognise (like default.aspx). As the module is in the ISAPI
pipeline, you can intercept the request before it gets processed by asp.net
as a file, and seen as an unknown file type.
--
Regards
John Timney
Microsoft Regional Director
Microsoft MVP
----------------------------------------------------------------------------
------------------------------------
<blatant plug>
Professional .NET for Java Developers with C#- ISBN: 1-861007-91-4
Professional Windows Forms - ISBN: 1861005547
Professional JSP 2nd Edition - ISBN: 1861004958
Professional JSP - ISBN:
1861003625
Beginning JSP Web Development - ISBN: 1861002092
</blatant plug>
----------------------------------------------------------------------------
------------------------------------
"Sean" <se**@hotmail.com> wrote in message
news:uT**************@TK2MSFTNGP10.phx.gbl...
Hi all,
Is it possible to use a custom HttpHandler to handler request that does
not provide a specified page?
e.g. http://www.aaa.com/there/is/no/such/document
I tried to handle this request using a custom HttpModule, but IIS directs
the request to an error page(404 file not found) before delegating to
ASP.NET.
Regards
Sean