Last post Oct 08, 2010 09:14 AM by w0lfshad3
Feb 21, 2010 02:54 AM|ravesoft|LINK
Directory Listing Denied This Virtual Directory does not allow contents to be listed with url rewriting in asp.net.
In Win server 2008 and iiS 7. when are look main page its can viewable, when we are click sub menu. we got this error.
Please help me.
Feb 21, 2010 04:11 AM|adeelehsan|LINK
Have you configured your virtual directory to allow the directory browsing rights? If you want to see the direectory listing, you have to enable this permission in the IIS.
Normally when you access some URL, for example http://yoursite/folder this will try to find the default document in that folder which are configured in the IIS and are index.htm, default.htm, default.aspx, index.aspx etc.
Make sure that when you click on the sub menu, you are accessing a page, not a folder. OR allow the virtual directory to display directory browsing.
asp .net 2.0
Feb 22, 2010 11:35 AM|ravesoft|LINK
Thank you buddy, for your great answerr, but when click my sub menu, i'm doing url rewriting internally.
http://xxxxx.webhost4life.com/cgmart/ --- > http://xxxxx.webhost4life.com/subfolder/list.aspx?ID=0987
this acutlly we doing internally,so how we can solve this?
thank you once again.
Feb 23, 2010 01:32 AM|night_dog|LINK
Here is a nice article which describes the problem:
Feb 23, 2010 03:45 AM|ravesoft|LINK
Hi thank, but there is no ant hint about IIS 7 and this issue.
Please give me working solutions
Feb 23, 2010 04:20 AM|night_dog|LINK
Which Url rewriting module are you using? Here are some more links
You can make it work like iis6 using a wildcard map:
Or you can check the Url rewrite module:
There are also other options:
Oct 08, 2010 09:14 AM|w0lfshad3|LINK
In my case it was because ISP changed my IP, w/o me knowing about it (hosting from my PC), and do some redirecting using a free subdomain. Although apparently unrelated to the error, this is what fixed it (was thrown off that localhost was doing it, had
forgotten about the redirects - site began working instantaneously after i updated the IP subdomain map). Going through a checklist of prerequisites needed for the site to work weeded out the problem. Error message was absolutely unhelpful.