Posted by dorayme on 01/10/07 22:34

In article <45a5071d$0$8941$4c368faf@roadrunner.com>,
Carl Pearson <jman_spam_trap_.org@gmail.com> wrote:

> dorayme wrote:
> > Could someone kindly recommend either a simple tute on the
> > subject or else a simple guide of the steps to be taken to make a
> > login page for a website so that a few password issued people can
> > view a particular set of pages or section of a website. It is not
> > needed to be like Fort Knox, just a simple thing like say a
> > commercial site where only wholesale customers are allowed into
> > some set of pages giving special information for their eyes only.
> >
> > I suppose it depends on the type of server as to what is best,
> > but assume a Unix with PHP enabled. I have got to the stage of
> > being able to use php includes both for Unix commercial servers
> > and my own on my Mac (in no small measure due to guidance on this
> > ng a while back).
> >
> > I am easily blinded by science! I know roughly what an .htaccess
> > file is and I have access to more than this on my own server, but
> > not more on commercial servers that host various sites I have
> > made or maintain.
> >
>
> There are a plethora of canned scripts out here to do this. Google "php
> authorize user".
>
> Below is some code I've been using for a few years. It probably needs
> updating.
>
> You'll need a database, to store the user's info (name, password,
> allowable group, etc.)
>
> Embed a script in every page for which you may wish to restrict access,
> which calls a validation function. This function compares some cookies
> that get set when the user h...

Thank you for taking the trouble and I have saved your script and
instructions for when I have a better grasp of these matters.
Stuff about cookies and databases is not something I am yet
familiar with on the website making side.

--
dorayme

[Back to original message]