I asked a similar question a while back. There were many great responses, I found one of merlyn's columns (Web Techniques Column 61 - May 2001) in his The Web Techniques Perl Columns to be very helpful.
in reply to CGI Session 'security' for in-house app.
I think you're on the right track. Here's what I think would be a good approach to the problem:
Hope this helps.
- Users login to the system.
- The system validates the user's name and password and assigns a session key into a cookie and a log file. (see merlyn's column)
- Every time the user goes to a page, the CGI checks the cookie and compares it to the log file, if the user is valid, it will render the page. If the user doesn't validate, the form won't even render for them. This should stop any wandering users for "accidentally" finding a form and submitting data to it.
I'm sure Edison turned himself a lot of colors before he invented the lightbulb. - H.S.