Re: [cobalt-users] Raq 2 & Raq 3 Filtered Login Security

["Simon Weller" <simon@xxxxxxxxxxxxx>]

Another option to .htaccess is by using session management.

You create a session when they log in, make them carry it around while 
they're on the site, and then write into your code to expire the session after x 
number of hours.

- Si

> "Web Doctor" <nywebdocter@xxxxxxxxxxx> writes:
> 
> > We need to filter or funnel all accesses to any page on web site to a front 
> > door login page than will verify the user's name, password, and access 
> > rights via a DB before granting access to ANY page on the web site. We do 
> > not want anyone to bookmark a static page and bypass the front door security 
> > either.
> 
> > We do NOT want to use htaccess because there will be over 5000 different 
> 
> Why do you keep avoiding the right solution?
> 
> Use .htaccess with a database backend for storing users and
> passwords. 
> 
> It surely will deal with 5000 users - and even many more.
> 
> 
> -- 
> Jens Kristian Søgaard,
> jk@xxxxxxxxxxxx -- http://www.jksoegaard.dk/
> Søger du noget? -- http://www.google.com/
> 
> 
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> To Subscribe or Unsubscribe, please go to:
> http://list.cobalt.com/mailman/listinfo/cobalt-users
> 



----
Simon Weller
NZ Servers
Professional Hosting Services into the new millennium
Specialising in Web and Database Development
http://www.nzservers.com