index.htm being renamed to index.html on publishing

[Guest]

This is something I never want, as even Apache etc. understand the .htm
extension nowadays. How can I turn it off?

The background is that I test releases on a development server, and I get a
different home page extension depending on whether I copy the release from
development to live via FTP, or re-publish using FrontPage. This then affects
Google Analytics etc.

 

[Ronx]

The home page is set by the server configuration. If the server
requires the home page to be named index.html (as is usual for *nix
servers), then FP will rename the page to be index.html.
Configure the server configuration files to allow index.htm as a default
page.
Using FTP on an extended site may corrupt the extensions, but FTP has no
intelligence, and ignores default page requirements set by the server
configuration.

 

[Guest]

The server doesn't 'require' the home page to be named index.html, it's
perfectly happy for it to be called index.htm (the relevant Apache
DirectoryIndex directive has been issued in this particular case, and this is
now the norm for Apache servers). FrontPage is officiously doing something
not asked for, without first checking to see whether it is unnecessary.
Anyway, all I want to do is to turn this behaviour off. Does anyone know how?

 

[Tom Willett]

The change *is* being made by the host server. Contact them.
--
===
Tom Willett
Microsoft MVP - FrontPage
---
FrontPage Support:
http://www.frontpagemvps.com/
===
| The server doesn't 'require' the home page to be named index.html, it's
| perfectly happy for it to be called index.htm (the relevant Apache
| DirectoryIndex directive has been issued in this particular case, and this
is
| now the norm for Apache servers). FrontPage is officiously doing something
| not asked for, without first checking to see whether it is unnecessary.
| Anyway, all I want to do is to turn this behaviour off. Does anyone know
how?
|
| "Ronx" wrote:
|
| > The home page is set by the server configuration. If the server
| > requires the home page to be named index.html (as is usual for *nix
| > servers), then FP will rename the page to be index.html.
| > Configure the server configuration files to allow index.htm as a default
| > page.
| > Using FTP on an extended site may corrupt the extensions, but FTP has no
| > intelligence, and ignores default page requirements set by the server
| > configuration.
| > --
| > Ron Symonds - Microsoft MVP (FrontPage)
| > Reply only to group - emails will be deleted unread.
| > FrontPage Support: http://www.frontpagemvps.com/
| > http://www.rxs-enterprises.org/fp
| >
| >
| >
| > | >
| > > This is something I never want, as even Apache etc. understand the
..htm
| > > extension nowadays. How can I turn it off?
| > >
| > > The background is that I test releases on a development server, and I
get a
| > > different home page extension depending on whether I copy the release
from
| > > development to live via FTP, or re-publish using FrontPage. This then
affects
| > > Google Analytics etc.
| >
| >

 

[Jens Peter Karlsen [FP-MVP]]

If more than one home page name is allowed, Frontpage will pick the
first in the list. You can't do anything about that, only the server
administrator can.

Regards Jens Peter Karlsen. Microsoft MVP - Frontpage.