Each of the 10 links will include a QueryString value, i.e.
requestedpage.asp?pswdtype=01
requestedpage.asp?pswdtype=02
requestedpage.asp?pswdtype=03
....
Part 1:
When requestedpage.asp is loaded, a script ensures that the request
to load requestedpage.asp came from a click on a link from the page
used to request and load requestedpage.asp. That would be done
using Request.ServerVariables("HTTP_REFERER"). This prevents
requestedpage.asp from being loaded by typing its URL into the
browser or by recalling requestedpage.asp as a saved Favorite.
If the HTTP_REFERER variable is empty redirect to sorrycharlie.asp.
Part 2:
Once the HTTP_REFERER is validated the script uses the
Request.QueryString method to get the QueryString values such as
01, 02, 03 and so on where each value is a symbolic 'rule' that your
script will 'know' how to determine which secure password is required
to continue loading requestedpage.asp and which users are permitted
to log into requestedpage.asp using a user name and password. A
database is generally required to achieve this latter part of the process.
That's the basics I've used for my customers who needed this type of
functionality on the e-commerce sites I've coded for. Its somewhat
common for membership systems and sites that required different levels
of access for different business partners.
--
<%= Clinton Gallagher
A/E/C Consulting, Web Design, e-Commerce Software Development
Wauwatosa, Milwaukee County, Wisconsin USA
NET csgallagher@ REMOVETHISTEXT metromilwaukee.com
URL
http://www.metromilwaukee.com/clintongallagher/