September 2007
Intermediate to advanced
600 pages
20h 21m
English
When you are dealing with sensitive information, such as account or purchase histories, you need to be more careful when passing parameters from page to page. It’s easy to let yourself feel that your work is done after you force your users to log in. Of course, forcing them to log in is an important step, but your code still needs to check things internally before it exposes sensitive data.
Here’s a scenario that illustrates a potential vulnerability. After putting together the OrderHistory.cfm template shown in Listing 23.4, you realize that people will need to be able to see the details of each order, such as the individual items purchased. You decide to allow the user to click ...
Read now
Unlock full access