Home/ Questions/Q 8277223
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-08T08:37:38+00:00

I’m using IIS7.5. I have a simple ASP.NET webforms site that uses basic URL

  • 0

I’m using IIS7.5. I have a simple ASP.NET webforms site that uses basic URL rewriting in global.asax, intercepting requests for .aspx pages and passing them to various template pages.

For example, you can request http://www.mysite.com/default.aspx. In global.asax I first check if this exists as a “true” page. If it doesn’t, I go off to the data store to get the details and redirect to template.aspx?page=default (or something similar).

This all works great. However, there’s one issue. If I browse to http://www.mysite.com/default.aspx I get the page I expect. If I set the default document to default.aspx, either in the web.config or in IIS, then browse to http://www.mysite.com/ I get the error about directory browsing not being allowed.

Why is IIS ignoring the default document in this case? It appears to be because the file “default.aspx” doesn’t exist. If this is the case, is there a workaround for the problem?

EDIT

To clarify, I don’t have control over the IIS system and it’s on really basic hosting, though I can request some changes, so I can’t use any URL rewriting modules.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Workaround for you situation: Create Index.aspx as default document as physical file and redirect user to Default.aspx URL. So when user comes to mysite.com/ then index.aspx will kick in and force redirect to default.aspx which can then handle your template redirection logic.

    • 0