Adventures As Me


Mucking through ASP

Written 19 May 2005

Being the Company’s only resident web developer I am tasked with maintaining, upgrading and adding features to our Intranet. An Intranet developed over a number of years by various people, all lacking various degress of knowledge, entirely developed in Front Page.

Recently Corporate upgraded the Intranet server to Windows Server 2003. One of the default features, security-wise, is accessing parent folders using the ‘..’ nomenclature is now verboten in scripts. Of course one can turn it on, but there go your security benefits. With the way worms attacked IIS in the past, one understands why leaving it disabled is a good thing.

However, FrontPage (at least 2000, the version we are using) wants to use the ‘..’ method of accessing the parent folder in its include tags. The solution is easy, change the include from a file type to a virtual type. Easy. Find all the include’s and change them. The Intranet works. Until someone else decides to modify part of the site using, you guessed it, Front Page. Which proceeds to redo all the include statements.

I would like to ban Front Page.

Related Posts