Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

we are in the middle of setting up a website and one of the developers has asked me a question im a little but stuck on.

basically we have a website that a user can visit and create there own "virtual" subfolder group.

so for instance, you would visit www.mydomain.com/index.aspx and signup a free account. At the end of this process this would give you a URL to your new website.

www.mydomain.com/yourwebsite/index.aspx

now the "yourwebsite" folder is done using URL rewritting from the asp.net application, it never exists on the website ever. my problem is that if the user decides to visit

www.mydomain.com/yourwebsite/ they get a 404 Page Not Found error, is there a way within IIS7 to resolve this, as in my eyes the behaviour is correct as the folder does not exist so IIS cannot find it to display the contents of it.

any advice would be appreciated.

Kris

share|improve this question
    
Can you post how you are rewriting the URLs? That may help in trying to come up with an answer. –  Rob May 19 '11 at 13:22
    
according to our developer they are using an ASP component (Found here urlrewriting.net/149/en/home.html) to-do the re-writing, the rules for this are in the web.config, i have copied what i can from the web.config file below. –  Kristiaan May 23 '11 at 12:43
    
turns out the comment box is not large enough to take the web.config file –  Kristiaan May 23 '11 at 13:38
add comment

2 Answers

Have you added index.aspx as a default document within IIS on your website? That is not included as a default document out of the box, you need to add it.

share|improve this answer
    
Hi Rob, thanks for the reply, i have tried to add index.aspx into the base websites default documents section however this has no affect when trying the URL again. –  Kristiaan May 19 '11 at 13:21
add comment

This problem turned out to be our lack of experience with the URL ReWrite component that we were using.

Once the developers looked at the data in the web.config file closer they spotted an obvious problem with it, after correcting this it worked fine.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.