David
Sun May 23 01:13:57 CDT 2004
There is no straight-forward way to "manage .aspx functionality on a
per-site basis" because that is not a feature.
Web Service Extension is a global setting in IIS6. It does not have the
granularity to support managing .ASPX functionality on a per-site basis.
What you CAN do is enable Web Service Extension (so ASPX pages can run
everywhere), and then on a per website (or per-vdir/app) level, remove the
.ASPX mapping to aspnet_isapi.dll. This will cause those .aspx pages to
not be executed as ASP.Net pages but treated as static files... and since
.aspx extension is not in the MIME Type, IIS6 will not allow them to be
downloaded and instead return a 404. You need to be careful with this
approach to never add .aspx as a MIME Type anywhere because that immediately
allows IIS to serve the file as-is -- which means you've just made an
information-disclosure security breach on your web server.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"WebGuyBob" <anonymous@discussions.microsoft.com> wrote in message
news:90F184D8-5529-4D73-BC14-5E96EE8072B1@microsoft.com...
Hi, folks. Here's the answer...
After googling many phrases and bouncing around from site-to-site, I finally
landed on a MS Knowledge Base article that solved my problem. In short,
although I registered .NET with IIS, IIS had defaulted to "prohibit" ASP.NET
in the Web Service Externsions section in IIS. Here's the link to the KB
article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;315122
Look in the section titled: "Enable a Pre-existing Web Service Extension in
IIS 6.0"
Now what I'd like to know is (assuming that that setting controls all sites
managed by IIS) how to turn that off as a default for all sites and somehow
manage .aspx functionality on a per-site basis. Any takers on that?
Thanks,
Bob