Fusebox: Developing ColdFusion® Applications

Starting the Request

In Chapter 1, “The Arrival of Fusebox,” we discussed the basics of Fusebox and how all page requests go through the index.cfm. All <href> links, form actions, JavaScript redirects, <cflocation> tags, and <cfmodule> tags should point to index.cfm. But how do we guarantee that? Aren’t there problems if a user requests qry_DeleteUser.cfm directly from a browser? At best, the misguided user sees an error message. At worst, the user is able to delete users in the system. How do we fix this problem?

Application.cfm Always Runs First

There is a template that ColdFusion processes with each page request: Application.cfm (the capital “A” is for UNIX case sensitivity). In fact, ColdFusion processes Application.cfm before processing ...