Re: Parent Paths and IIS 6.0
From: Tom Pepper Willett (tompepper_at_mvps.org)
Date: 06/02/04
- Next message: Thomas A. Rowe: "Re: dynamic page titles and FP2003 DWTs"
- Previous message: Dan V.: "I cannot publish to our WebServer running IIS 5 from FrontPage 2003."
- In reply to: Thomas A. Rowe: "Re: Parent Paths and IIS 6.0"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 2 Jun 2004 10:50:10 -0500
Same here. We don't even use the INET Pub directory or the c drive.
-- ===================================================== Tom Pepper Willett [Microsoft MVP - FrontPage] ---------------------------------------------------------------------------- - Microsoft FrontPage: http://www.microsoft.com/office/frontpage/prodinfo/default.mspx http://msdn.microsoft.com/office/understanding/frontpage/ To assist you in getting the best answers for FrontPage support see: http://www.net-sites.com/sitebuilder/newsgroups.asp ===================================================== "Thomas A. Rowe" <tarowe@mvps.org> wrote in message news:OVERGbLSEHA.4020@TK2MSFTNGP11.phx.gbl... > 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) > http://www.ycoln-resources.com > FrontPage Resources, WebCircle, MS KB Quick Links, etc. > ============================================== > To assist you in getting the best answers for FrontPage support see: > http://www.net-sites.com/sitebuilder/newsgroups.asp > > "Kevin Spencer" <kspencer@takempis.com> wrote in message > news:OSEOMmKSEHA.2408@tk2msftngp13.phx.gbl... > > 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. > > > > "Thomas A. Rowe" <tarowe@mvps.org> wrote in message > > news:OQSRytBSEHA.2772@TK2MSFTNGP10.phx.gbl... > > > You can re-enable. There is no setting in FP to control this. > > > > > > -- > > > ============================================== > > > Thomas A. Rowe (Microsoft MVP - FrontPage) > > > WEBMASTER Resources(tm) > > > http://www.ycoln-resources.com > > > FrontPage Resources, WebCircle, MS KB Quick Links, etc. > > > ============================================== > > > To assist you in getting the best answers for FrontPage support see: > > > http://www.net-sites.com/sitebuilder/newsgroups.asp > > > > > > "Cathi Odtohan" <cathiodtohan@hotmail.com> wrote in message > > > news:h26vc.962$Jp.59017@ord-read.news.verio.net... > > > > 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! > > > > > > > > > > > > > > > > > > > > > > > >
- Next message: Thomas A. Rowe: "Re: dynamic page titles and FP2003 DWTs"
- Previous message: Dan V.: "I cannot publish to our WebServer running IIS 5 from FrontPage 2003."
- In reply to: Thomas A. Rowe: "Re: Parent Paths and IIS 6.0"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|