IIS Question

Good Morning!

We just purchased a .net domain...we are moving from a .com (which was managed by our parent company) to a .net, which we are managing.  I have a few questions, since we're kind of new to this side of the IIS world.

We have a lot of applications, and each will have their own page (www.domain.net/application).  However, if someone misses the page extension, we'd like www.domain.net to be a landing page that will have a link to each of our different pages for each application.

I've been trying to search for information on the Internet, but I'm having difficulting finding exactly what I need.  Can someone either give me some information or point me to a few good resources, please?

Thanks in advance!
bucball2007Asked:
Who is Participating?
 
Paul MacDonaldDirector, Information SystemsCommented:
Just build any old web page and make sure your web server points to it as the default document.  IIS looks for default.htm, default.asp, index.htm, and index.html when it's first set up, so you could name your page one of those if you like.
0
 
Paul MacDonaldDirector, Information SystemsCommented:
The answer depends a little on what you mean by "if someone misses the page extension".

The main site (www.domain.net) should have its own home page, of course.  If a visitor doesn't know the application name, going to the main site should just take them to that home page.  

If a visitor misspells an application name, you could have a custom 404 error page that tries to handle the request gracefully.  I have a page that tries to parse the URL sent by the visitor and looks for key words.  If I find something that is similar to a page I have (/docs instead of /documents), I send the visitor to what I think it is they're looking for.  Otherwise they get the home page.
0
 
Emmanuel AdebayoGlobal Windows Infrastructure Engineer - ConsultantCommented:
As Paulmacd suggested, you ca do this by customised error 404 page. For information on how to, pls check the link below

http://www.sherweb.com/blog/how-to-create-custom-error-pages-in-iis-7-5-with-asp-net/
0
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
bucball2007Author Commented:
Thanks for the info.  What I mean by "if someone misses the page extension"...if they go to www.domain.net instead of www.domain.net/app1, or www.domain.net/app2, can we have www.domain.net be the home page, but with the links to the app1 and app2 pages?  Kind of like a Contents page.
0
 
Paul MacDonaldDirector, Information SystemsCommented:
"can we have www.domain.net be the home page, but with the links to the app1 and app2 pages?"
Absolutely!  And it could be exactly as you describe - a page with links to the various applications.
0
 
bucball2007Author Commented:
Thanks paulmacd...where would I find documentation on that?  That's what I can't find.  :)
0
 
David Johnson, CD, MVPOwnerCommented:
<!DOCTYPE html>

<html lang="en">
    <head>
        <meta charset="utf-8" />
        <title>Main Page</title>
    </head>
    <body>
        <p><a href=".\app1\default.html">Application 1 </a></p>
        <p><a href=".\app2\default.html">Application 2 </a></p>
        <p><a href=".\app3\default.html">Application 3 </a></p>
    </body>
</html>

Open in new window

0
 
bucball2007Author Commented:
Thanks paulmacd and David Johnson!  :)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.