If you are receiving FORM fields or URL parameters that are not in Latin-1 encoding, use the SetEncoding() function to specify the character set to use. For example, to correctly process Japanese SHIFT-JIS characters in FORM fields you could use SetEncoding("FORM", "SHIFT-JIS"). (Applies to:...
The ColdFusion documentation is good, but it's even better when combined with updates and user comments. You can browse the updated docs (and add your own comments) at http://livedocs.macromedia.com/. (Applies to: ColdFusion 5 & MX)
no longer returns . (current directory) and .. (parent directory) entries as it did in CF5 and earlier. As such it is no longer necessary to filter out these entries when processing directory listings. (Applies to: ColdFusion MX)
now supports an optional CHARSET attribute which defines the character set of the URL being requested. The default is the server default (or UTF-8). If existing calls are failing or returning truncated or invalid data you might want to explicitly set the CHARSET as needed (use UTF-8 if you are...
Prior to ColdFusion MX, if you were caching pages that were accessed on a port other than port 80, you had to specify that port manually (using the PORT attribute). In CFMX now defaults to the port used for the requested page itself. (Applies to: ColdFusion MX)
The tag, used to provide access to the system registry, is no longer support on Unix versions of ColdFusion. (Applies to: ColdFusion MX)
If using the integrated HTTP server (standalone mode), custom error pages for specific HTTP errors (for example, 404) may be specified in the web.xml file in the WEB-INF directory. To add an error page add an XML branch entitled containing two items specifying the error code and specifying the...
ColdFusion MX generates Java source code for CFM pages and then compiles them into Java bytecode (.class files). By default the Java source (.java files) are not saved. You may change this behavior by modifying the web.xml file in the WEB-INF directory, setting coldfusion.compiler.saveJava to...
ColdFusion MX now supports evaluations within expressions (without needing the Evaluate() function). For example, #filesize/1024# is now allowed - before that calculation would have had to be done previously and saved to a variable, or an Evaluate() would have had to be performed. (Applies to:...
While ColdFusion MX primarily improves UDF support in the tag based interface, one very important enhancement was made to based UDF's too - they now support try/catch handling using the keywords "try" and "catch". (Applies to: ColdFusion MX)