snip
that will protect against people typing the url in their broswer to get the
code.
i'm not sure what you're talking about here...php code is parsed on the
server then the html is sent to the browseronly way to get code is
if there's a .phps copy of the file accessible on the web
If the include file has an extension that is not recognized by the server as
being a "PHP" file, the server will simply serve it up as text. So, your
file index.php is recognized as being a PHP file, it gets passed to PHP
which parses and compiles it and returns it to the server, which passes the
if someone knew the name of your include file, and it was under the
webserver root (for instance, the same folder) then yes, its like any
other file..you can get around this by changing your php.ini
include_path variables and putting the files there, outside the
webserver directory
I'd
If the include file has an extension that is not recognized by the server
as
being a "PHP" file, the server will simply serve it up as text. So, your
file index.php is recognized as being a PHP file, it gets passed to PHP
which parses and compiles it and returns it to the server, which passes
"... hate to think that someone could come along and just use it all for
free" So you don't really care to contribute to the Open Source community?
We would love to have your passwords. I would highly recommend setting an
include path outside the web server document root and store you files with
yes your code should be safe, at least from people trying to look at it
over the web...people on the server, well, that's another story...anyone
who can get into your www directory, and depending on the perms of your
files (if they have world readable) can view them...
i originally made some
Murph wrote:
Hi.
So, I've written all this nifty code and I'd like to do what I can from having it
pilfered.
What do you do to keep your stuff safe?
Murph
www.murphatnight.com
__
Brian Murphy - 193A Lowell St., Apt.
the much easier method is to change all your code extensions to be either parsed or
forbidden in httpd.conf
Files *.egn
AllowOverride AuthConfig FileInfo Indexes Limit Options
Order allow,deny
Deny from all
/Files
or
AddType application/x-httpd-php .inc
Actually, I think the best thing is to offer good service and value to your
customer
.
Then why would anyone want to invest the time to decompile your work to
change it?
On 3/14/01 8:30 PM, "Jack Dempsey" [EMAIL PROTECTED] wrote:
Murph wrote:
Hi.
So, I've written all this nifty code
9 matches
Mail list logo
