This should work as long as you are only including your include files from
scripts named index.php.
--Jacob
"Philippe Saladin" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > directly. My main question is if all of the code inside an included PHP
> file
> >
A monthly magazine for PHP Professionals. Get your copy
> today. http://www.phparch.com/
>
> > -Original Message-
> > From: Jacob Copsey [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, January 15, 2003 3:53 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: [PHP] Sec
t; wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> --- Jacob Copsey <[EMAIL PROTECTED]> wrote:
> > My style of PHP is to name all included files with a .php
> > extension and of course this raises the problem of people
> > accessing these script files
True. But let's just call me anal retentive. :-) Let's say I didn't have the
option of doing what you suggested. Are my ideas sound? Also, those ideas
apply to top-level PHP scripts in an application.
Jacob
"Kevin Stone" <[EMAIL PROTECTED]> wrote in message
007801c2bcd4$02d000f0$6601a8c0@kevin">n
I am beginning work on a new web-based application using PHP and MySQL. I
have been doing a lot of reading about PHP security and web application
security in general to make sure I am up-to-date on what is known in this
area.
My style of PHP is to name all included files with a .php extension and
5 matches
Mail list logo