Running classic asp page under

The server I am working on is 1.1

I’m trying to use form based authenticion on a section of the website. It contains a bunch of different types of content. This works fine for .htm, images, pdfs, etc… but when an asp page comes up I get:

[INDENT][COLOR=“Red”]Server Error in ‘/application’ Application.

This type of page is not served.

Description: The type of page you have requested is not served because it has been explicitly forbidden. The extension ‘.asp’ may be incorrect. Please review the URL below and make sure that it is spelled correctly.

Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300 [/COLOR][/INDENT]

I’m using a wildcard application map to make sure content is passed on to the forms based security.

ASP content is allowed on the server. (under web services extensions)

Any ideas why this is not being served up?

Because ASP.NET passes it to the ForbiddenHandler. And ASP.NET is running the page because of your wildcard mapping.

You should probably just bite the bullet and upgrade the page to ASP.NET.

Ahh if were only just one page!

In any case, I see now that I could remove the httpforbidden with asp from the machine.config. but this would just serve up the raw page.

But I find it hard to believe there isn’t a way that I can use a httphandler in web.config to pass it on to the asp processor.

<add verb=“" path=".asp” type=“?” />

Not really easily. Now, if you removed the wildcard handler, you could run the ASP pages side-by-side, but your forms authentication will not work within the ASP pages.

I have yet to see an interop scenario anyone was happy with . . .