Date: Tue, 16 Oct 2001 16:36:07 -0400 From: "Gerald T. Freymann" <freymann@scaryg.shacknet.nu> To: "Linh Pham" <lplist@closedsrc.org> Cc: <freebsd-questions@FreeBSD.ORG> Subject: Re: quick php/apache question re the tags Message-ID: <011201c15682$2f135d60$0f01a8c0@phantom> References: <20011016131318.M33262-100000@q.closedsrc.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> That's the why it's supposed to work. Apache handles .htm/.html files by > just reading them in and spitting the entire file, unchanged back to > the browser. Makes sense. > When it enoucnters a .php file, it reads it in and sends to the PHP > parser and Apache gets back the processed file and sends it to the > browser. Gotcha. > Why change it? Awh, to the meat of the problem. I'm working on an "admin portal" thing for work. I would like users to have to "log in" before they can access the admin pages. Right now I have simply used .htaccess to protect the directory and those below, and I'm thinking this may be the way to go as it's super easy, only requiring shell access to add usernames and passwords. I wonder what is better? passwording protecting a site with .htaccess or using some other kind of utility like http://www.phpsecurepages.f2s.com/ ? The latter pretty well requires every file to end in .php but can offer some nice web-based user management tools. .gf To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?011201c15682$2f135d60$0f01a8c0>