<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7226.0">
<TITLE>Re: [development] let's cleanup /misc</TITLE>
</HEAD>
<BODY>
<DIV id=idOWAReplyText3250 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>I am unsure how IIS would
react to the settings.php file being outside of the virtual directory or how to
configure it. Right now, unless you set the folder to allow for
this, you cannot browse files below the root unless specifically
allowed.</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> development-bounces@drupal.org on behalf
of Darrel O'Pry<BR><B>Sent:</B> Tue 1/10/2006 8:41 AM<BR><B>To:</B>
development@drupal.org<BR><B>Subject:</B> Re: [development] let's cleanup
/misc<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>On Tue, 2006-01-10 at 14:49 +0100, Bčr Kessels wrote:<BR>> Op
dinsdag 10 januari 2006 14:20, schreef Adrian Rossouw:<BR>> > The OSX way
is far far simpler, and much much cleaner.<BR>><BR>> But much unsafer (not
speaking of OSX vs Unix safety).<BR>> We discussed before, that PHP files
should really live in a non-web-acessible<BR>> place.<BR> -- I kind of
have to disagree with this... php files containing<BR>sensitive data
should not be in a web accessible<BR>directory(settings.php)... If you're
worried about people uploading<BR>randscript.php or rewriting your .php files I
think you have other<BR>things you need to address like permissions.<BR><BR>>
The biggest downside of that, indeed, is that the web-accessible files can
no<BR>> longer live in the module directories.<BR>><BR>>
Bčr<BR><BR><BR></FONT></P></DIV>
</BODY>
</HTML>