About mod_accessCookie:
=======================
In short, this module restricts access in the same way as an 'allow from'
does (it is derived form this module :), by checking for the exinstance of
a cookie. If a cookie is present it compares it to cookies found in a mySQL
database. If it can find a equivalent cookie there, access is granted, else
access is denied.


Features:
=========
* Compare a cookie to the COOKIE field in a mySQL Database
* Restrict by using additional fields in this Database
* Server-Side session management. Compare to the eTIME Field
  in the same Database if Cookie is expired.
* Add the fields named accessCookie_* from the database to the
  Apache environement (CGI programmers will love this)


Configuration:
==============
* Example:
		accessCookie_Engine on
		accessCookie_Server localhost
		accessCookie_Database test
		accessCookie_Table TestAuth
		accessCookie_Username wwwrun
		accessCookie_Password wwwpass
		accessCookie_Name harbor
		accessCookie_Timetrack distance
		accessCookie_Timetrack_Distance 600
		allowCookie use all

* accessCookie_Engine: Switch this one 'on' or 'off' to enable/disable the
  usage of this module. By default this is off.
* accessCookie_Server: Valid mySQL Server. localhost is the fastest
  and recommended solution.
* accessCookie_Database: Valid mySQL Database
* accessCookie_Table: Valid mySQL Table. The table must at least have a COOKIE
	char(..) field, if you want to use Timetrack you must also have a eTIME 
	timestamp(14) field. Every field you name like accessCookie_... will be 
	exported to the Apache environement.
* accessCookie_Username: User, that can access your table (SELECT, UPDATE)
* accessCookie_Password: Valid password of the user
* accessCookie_Name: Name part of the Cookie (Cookies have a name and a value 
	part). The module checks only for Cookies with this name.
* accessCookie_Timetrack:
	- 'off' does no checking 	of the eTIME field at all. 
	- 'static' checks if the eTIME field is >= NOW. Soif this field is smaller 
		than the NOW value, access is denied. 
	- 'distance' does the same as 'static' but also sets the eTIME field to 
		NOW + 'Timetrack_Distance' Seconds. With this Option you can do safe
		Session management.
	By default this is off.
* accessCookie_Timetrack_Distance: An amount of Seconds to add to the eTIME 
	field if 'Timetrack' is set to 'distance'.
* allowCookie:
	- use all: Use all rows of the mySQL database to search for the COOKIE
	- use none: Use no lines of the mySQL database to search for the COOKIE.
		This will deny access to everyone.
  - where ...: Use only the rows, that match the ... mySQL where Statement.
    You can use this to manage different subgroups of users (that use the same
		login mechanism)
  NEW NEW NEW NEW NEW NEW NEW
  - keep alive: don't deny users but if if existing valid cookie, update there
    eTIME. Works only in conjunction with "accessCookie_Timetrack distance"


How to use this Module:
=======================
* Write a HTML page where your users can type in their usernames and passwords
* send the data to a cgi that decides, who is a valid user, and who is not.
* send a COOKIE named accessCookie_Name with a random, unique value of your 
  choice to the user.
* save the value also to the mySQL Table name accessCookie_Table into the 
  field COOKIE.

=> now the users that have the right cookie can access the directory you
   secured with the accessCookie module.

* Write a cleaning procedure that kicks out the expired COOKIES every night.


Usefull Stuff:
==============
* If you use Timetrack it is easy for you to write a little Program (i use
  web pages) to show how many users are active at the current moment. Your boss
  will love this feature.
* If you are using for example php in the directory, the exported allowCookie_*
  values save you some work. e.g.: Show your users who they are, without 
	additional Querys.


Why should I use Timetrack:
===========================
Why should I use Timetrack, I could set the 'expires' value of my cookie,
this is much easier for me!

Ah, you trust the client's browsers to don't send you the cookies if they 
are expired.
Hm, you don't have to be a very skillful	programmer to write your own browsing 
tools that send the cookies you want them to send. Once got the cookie => 
access forever (or at least for some uncontrollable time). 
If you are using a Server based expire you have exact control about the 
time the user can access your server. Or lock him out, by simply changing the
his eTIME field. 

Command line browsing tools, libraries: curl(libcurl), libwww(w3c), differnt 
perl modules.


LICENSE:
========
Read the Apache License, and the lines in front of the mod_accessCookie.c
