From: ma_khan on 8 Aug 2008 13:06
A few quick things...
Directory Browsing and Default Document are 2 seperate modules within IIS 7
403 responds to Access Denied and 401 responds to unauthorised ...
if default.aspx is a local file and was then added to the default document
list then you should be having the following entry in the web.config file
<add value="default.aspx" />
check if you have this...
"Anthony Jones" wrote:
> This is probably an embarrassingly simple problem but I can't seem to find
> an answer.
> I'm testing an existing site which is a mix of ASP/ASPX with ISAPI filters
> and trying to get it to run on IIS7.
> I have the pool configured as 32 bit and classic pipeline.
> The various pages seem to work fine but I can't seem to get the default
> documents to work.
> E.g., http://mysite.domain.com/ should simply execute default.aspx.
> I have directory browsing turned off and default.aspx is at the top of the
> default document list.
> Visiting default.aspx specifically works fine. In deeper folders which also
> have default.aspx or default.asp I'm getting 401.
> Any Ideas?
> Anthony Jones - MVP ASP/ASP.NET
From: Anthony Jones on 8 Aug 2008 14:11
"ma_khan" <makhan(a)discussions.microsoft.com> wrote in message
> A few quick things...
> Directory Browsing and Default Document are 2 seperate modules within IIS
> 403 responds to Access Denied and 401 responds to unauthorised ...
> if default.aspx is a local file and was then added to the default document
> list then you should be having the following entry in the web.config file
> <defaultDocument enabled="true">
> <add value="default.aspx" />
> check if you have this...
Those entries are present. However it leaves me a little confused. Does
the classic pipeline use the web.config?
Still scratching my head on this one? :(
Anthony Jones - MVP ASP/ASP.NET
Prev: Unable to install IIS 6 Metabase and IIS 6 Configuration Compatibi
Next: ASP Log Out script