ColdFusion's Server-side Form Validation

ColdFusion's built in server-side form validation often gets a bad rap, but this past week it really came in handy. For those that don't know, ColdFusion can do certain types of server-side validation depending on how you name your form fields. All you need to do to trigger this validation is add a suffix to your form field name. Here are the available validation options:


SQL Formatting

This is something that drives me crazy. The other day I needed to debug a problem report so I asked the developer to send me SQL he was using to generate the report. The SQL looked something like this:


ColdFire 0.0.6

On Sunday Ray quietly released version 0.0.6 of ColdFire. With this version, the ColdFire extension actually modifies the user agent by adding "ColdFire/0.0.6" to the end of the string. This allows the coldfire.cfm debug template to check the user agent header for this string and only return debugging info if it is present. This means you shouldn't encounter much debugging overhead if you don't have ColdFire installed or if you choose to disable Firebug for your site. ColdFire only modifies the user agent header if Firebug is enabled.

While this may seem like a minor update it actually involved some major changes to the FireFox extension code. The biggest change was the addition of an XPCOM object to handle the request header modification. Compiling an XPCOM typelib requires the Gecko SDK and unfortunately there isn't an Intel Mac build of the SDK. While I could have tried to build it myself, in the interest of time I ended up switching to my PC for extension development. Even then, building the typelib wasn't exactly straightforward. If you find yourself trying to build a XPCOM component on Windows you may find the following helpful: Find xpidl.exe in Gecko SDK for compiling IDL files.

Anyway , enjoy and look for more ColdFire updates soon.

BlogCFC was created by Raymond Camden. This blog is running version 5.8.001.