Skip to main content

ColdFusion 10: CFFILE - Specifying file content in the tag body

Prior to ColdFusion 10, to write or append to a file one had to specify the file content in the output attribute of CFFILE tag. In ColdFusion 10, you can specify the file content in the body of the cffile tag. In cases where the file content is specified in body as well as in the output attribute, the output attribute would be ignored.

Example:

<!--- output attribute will be ignored here ---> <cffile action="write" file="#expandPath("./files/employees.txt")#" output="cffile content"> <?xml version='1.0' encoding='UTF-8'?> <employees> <id = "1"> <firstname>Sagar</firstname> <lastname>Ganatra</lastname> </id> </employees> </cffile>


As observed, the output attribute would be ignored when the file content is specified in the tag body. The above example is also applicable when the action attribute is set to append. This enhancement makes it easy to write any data to a file without having to use the CFSAVECONTENT tag and a temporary variable.

Another important thing to note here is that the output attribute is now optional when action is write\append. However, it is a mandatory attribute when the closing CFFILE tag is not specified:


<!--- Output attribute is mandatory when the closing tag is not specified ---> <cffile action="write" file="#expandPath("./files/employees.txt")#" output="No body" >

Comments

  1. This is certainly a nice enhancement, however, does it actually validate that the *content* of the file matches the mim type, or is it simply checking the value of the mime-type header that is sent by the client?  Simply checking the value of the mime-type header without validating the content of the file doesn't really add much security, since it's easy to fake that header.

    ReplyDelete
  2. @ec42b1f555169f2e36a71b3bf2249187 did you see this post: 
    http://www.sagarganatra.com/2012/03/coldfusion-10-cffile-restricting-file.html. Now you can validate the content when you upload a file to the server.

    ReplyDelete

Post a Comment

Popular posts from this blog

File upload and Progress events with HTML5 XmlHttpRequest Level 2

The XmlHttpRequest Level 2 specification adds several enhancements to the XmlHttpRequest object. Last week I had blogged about cross-origin-requests and how it is different from Flash\Silverlight's approach .  With Level 2 specification one can upload the file to the server by passing the file object to the send method. In this post I'll try to explore uploading file using XmlHttpRequest 2 in conjunction with the progress events. I'll also provide a description on the new HTML5 tag -  progress which can be updated while the file is being uploaded to the server. And of course, some ColdFusion code that will show how the file is accepted and stored on the server directory.

Server sent events with HTML5 and ColdFusion

There are several ways to interact with the server apart from the traditional request\response and refresh all protocol. They are polling, long polling, Ajax and Websockets ( pusherapp ). Of all these Ajax and Websockets have been very popular. There is another way to interact with the server such that the server can send notifications to the client using Server Sent Events (SSE) . SSE is a part of HTML5 spec:  http://dev.w3.org/html5/eventsource/

De-obfuscating javascript code in Chrome Developer Tools

I had blogged about JavaScript debugging with Chrome Developer Tools  some time back, wherein I have explained how these developer tools can help in debugging javascript code. Today Google Chrome 12 was released and my Chrome browser was updated to this version. As with every release, there have been some improvements made on performance, usability etc,. One feature that stood out for me is the ability to De-obfuscate the javascript code. What is Minification? Minification is the process of removing unnecessary characters such as white spaces, comments, new lines from the source code. These otherwise would be added to make the code more readable. Minifying the source code helps in reducing the file size and thereby reducing the time taken to download the file. This is the reason why most of the popular javascript libraries such as jQuery are minified. A minified jQuery file is of 31 KB in size where as an uncompressed one is about 229 KB. Unfortunately, debugging minified javascript f...