Custom Http Handler Question

[Mark Olbert]

I have a custom http handler set for an ASP.NET site which handles requests for ".scef" pages. It
works fine once IIS is properly configured.

I've noticed something about the handler, though, that I want to confirm. Let's say my site has a
"virtual" page that the handler should generate called www.scef.us/test2.scef. If I enter that
address in the address bar of a browser -- and the site's ASP.NET process isn't running (it's not a
heavily-trafficed site) -- I get a server application error.

But if I first visit a "normal" page in the site -- say the home page, which is a plain aspx page --
then visiting the virtual page works fine.

It's as is asking for the virtual page doesn't cause the site's process to start. At least, that's
my theory.

Is this theory correct? If so, how do I code an http handler so that it will start up the site
process? If the theory's not correct, what other things might be causing this behavior?

Thanx in advance!

- Mark

 

[Daniel Fisher\(lennybacon\)]

How do you configre IIS - map the extension to the aspnet ISAPI?

 

[Daniel Fisher\(lennybacon\)]

That is the right way