Parent Paths and IIS 6.0

C

Cathi Odtohan

We recently upgraded our WindowsNT 4.0 server with IIS 4.0 to WindowsServer
2003 with IIS 6.0.
EndUsers are using FrontPage Server 2002 to generate web pages.

One of the security features of IIS 6.0 is default disabling of Parent
Paths. Unfortunately, when FrontPage 2002 generates *.asp pages using the
Database Results Wizard, the #include statements always use relative parent
paths. Is there a way to make FrontPage2002 use absolute paths? Is this
problem resolved in FrontPage2003?

Any advice is appreciated.
Thanks!
 
T

Thomas A. Rowe

You can re-enable. There is no setting in FP to control this.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
 
K

Kevin Spencer

Unfortunately, allowing parent paths CAN lead to attacks on your web server,
which is why it is disallowed by default. However, you can overcome this by
putting your web server's directories on a different drive than the
Operating System.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
 
T

Thomas A. Rowe

At least with my web host, websites are not stored on the OS boot drive of the server, so it is safe
to allow the use of Parent_Paths.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top