Need Help With Publishiing To Web Server

[Guest]

I created a website in FrontPage 2003 and published it to
a test directory within the main directory of my website
(www.mysite.com). Everything worked fine until I tried
to publish the same files and folders to the main
directory. I am now getting a page cannot be displayed
error (IE 6.0).

I've been working with my hosting provider (Interland)
and it appears that we've identified the problem, but
cannot fix it. My home page (index.asp) contains a line
of html code that is trying to access a file <!--#include
file="../_fpclass/fpdblib.inc"--> that is not in the
indicated directory. The "../" seems to be the cause of
the problem, and is uneccessary since my web pages exist
witin the root directory and the _fpclass folder is one
level down (not up from the root). The strange thing is,
when I view the html of the index.asp page through
FrontPage, I do not see the ../. I only see it when
viewing the page through notepad.

I suspect that the shared border on the index.asp page
may be the cause of this problem since it needs the ../
to go up a directory to access the hyperlink pages
contained within it. I noticed that the ../ command
occurs within a shared border section.

We've tried to delete the ../ from all the pages but
FrontPage seems to keep regenerating it in all the
webpages. We've tried reinstalling the extensions and
pretty much everything else we can think of. Can you
please help!

Thanks!!!

Andy G.

 

[Darrell]

There is an article in microsoft technet about this exact
issue. You will need to have the "enable parent paths"
selection enabled on the IIS server application
configuration to stop this error. I would suggest you
look at the Technet article as it has warnings etc... but
it will certainly fix your issue..

Good luck

Darrell

 

[clintonG]

Security concious ISPs are no longer supporting parent path
configurations as parent paths have been used to hack through sites
enabling the traversal of the file system.

Doesn't FrontPage use a meta tag to load the shared borders
at runtime? Get rid of the meta tag and you may get rid of the
parent path reference. In fact, I thought it has been commonly
recommended to get rid of shared borders as they are not worth
the problems they have caused.

--
<%= Clinton Gallagher
A/E/C Consulting, Web Design, e-Commerce Software Development
Wauwatosa, Milwaukee County, Wisconsin USA
NET (e-mail address removed)
URL http://www.metromilwaukee.com/clintongallagher/