Recent Topics

an idea to handle users when they access files they cant

Started by on Mar 26, 2007 – Contents updated: Mar 26, 2007

Mar 26, 2007 04:05    

Well, this is a easy suggestion: instead of using

if( !defined('EVO_MAIN_INIT') ) die( 'Please, do not access this page directly.' );

in the files that cannot be directly accessed by the users, won't be better to use something like:

if( !defined('EVO_MAIN_INIT') ) header("Location: http://www.wherever.com/");

My idea is -basically- to be practical and tell the user "go to the "cover/error page/wherever you like" of the site if u went to some file u cant directly access". My 2 cents... :P

PS: Or maybe could be pointed to a certain "error page", instead of printing a tiny "dont do" line (with graphics would look a lot nicer this very same warning... and this is code-savy, instead of putting a lot of code!)

Mar 26, 2007 16:00

I never gave it much thought, but if I was interested in making a change I'd have to re-do every release I'd go with something like

if( !defined('EVO_MAIN_INIT') ) die( 'fail' );


Figure the "visitor" is poking around in places they've got no reason to be poking around in, so why waste even a byte talking to them at all?


Form is loading...

Community software – This forum is powered by b2evolution CMS, a complete engine for your website.