The public content is easy, standard stuff.
The static group content will be items such as information, forms, and downloads which is available to any and all approved users.
The dynamic private content is specific to user. These would be reports composed of information specific to the exact user.
The dynamic private content will be served through Perl scripts. This will most likely be controlled by cookiers following a successful login.
I would rather control access to the static group content via htaccess authenticate so that update of the pages does not intermingle with the Perl scripts. This allows a slightly less trained person to do the updates. HTML and FTP knowledge rather than Perl background. i.e. cheaper labor for da boss.
Obviously the easy solution is to have the users login twice. Once when they need access to the group material, and then again when they need access to any private material.
Da boss is annoyed by the double login and I'm trying to find a way around this. Hence the grasping at straws....
Thanks, Claude
In reply to Re: Re: Calling script after htaccess authentification
by Xxaxx
in thread Calling script after htaccess authentification
by Xxaxx
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |