Welcome to WebmasterWorld Guest from 23.23.53.177

Forum Moderators: open

Message Too Old, No Replies

Expression Web creates pages named default.htm

Is this good or bad

   
9:31 pm on Oct 2, 2007 (gmt 0)

10+ Year Member



When I create a new site using Expression web it names the pages default.htm instead if index.htm or index.html

For instance the home page is default.htm.

I had to reconfigure my server to treat default.htm as an index page, but otherwise everything is fine.

What are the advantages of using default.htm -- or should I change the page names to index.html?

5:02 am on Oct 3, 2007 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I do not think it makes a difference. Though I can reset the default home page on the server too, I am use to having the default home page as index.whatever, so I change default.htm to index.htm. I have searched EW on how to change the default page setting, but to no avail. (If anyone figures it out, please let me/us know)

In the end, I think it is
a) what you are comfortable with and
b) the ability to set the default home page on the server.

Otherwise, very few people I know type the page extension when initially going to a web site's home page.

Marshall

5:10 am on Oct 3, 2007 (gmt 0)

WebmasterWorld Senior Member vincevincevince is a WebmasterWorld Top Contributor of All Time 10+ Year Member



Using default.htm is a delightful way for Microsoft to make a few users decide that Apache doesn't work and that they need to use IIS.
11:56 am on Oct 3, 2007 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Well since nearly any server can be set to serve up any of a list of pages as the default home page, I think that the MS conspiracy theory is a bit much.
12:03 pm on Oct 3, 2007 (gmt 0)

WebmasterWorld Senior Member vincevincevince is a WebmasterWorld Top Contributor of All Time 10+ Year Member



I think that the MS conspiracy theory is a bit much

IIS supports default.htm out-of-the-box. Apache does not support it without extra configuration. For the new WYSIWYG webmaster, finding that their new site "doesn't work" with Apache is as likely to end in using IIS as it is in them first finding the problem and then reading the Apache documentation to find the solution.

It is hard to see this as anything but making IIS more attractive to Expression built sites. Sure, it may be a small thing, but there's a limit to the number of minor annoyances someone's willing to go through just to use Apache.