This project is read-only.

How to launch my filter before aspx processing mechanizm?

Nov 28, 2008 at 12:24 PM

I want to launch my filter before IIS start processing aspx files and other predefined Asp.Net extensions.

For example:
1) user trying to open an aspx page
2) our filter intercepts this request
3) using some algo it will decide: to pass request to the aspnet isapi or to cancel it.

Any suggestions of how to implement it?

Because my current test shows that my filter fire ups after page processing.

Best regards, Artur Okolity.
Nov 28, 2008 at 9:30 PM
Hi Arthur,

The Filter.NET framework is a managed wrapper around ISAPI Filters, so any managed filter is launched and executed before (if you handle the appropriate notifications like OnPreProcHeaders for example) the request reaches any ISAPI Extension, in particular, the ASP.NET ISAPI Extension, ASP, etc ...

How do you see the filter firing up after the ASP.NET page?

Tiago Halm
Dec 2, 2008 at 2:15 PM
Hi Tiago,

OnPreProcHeaders everything is working ok.
Maybe a was using different notification.