Comments on: Secure image uploading with ColdFusion

By: anon

anon — Tue, 24 Jan 2012 08:38:35 +0000

ColdFusion has an attribute you can specify in cffile ‘nameconflict’, set this attribute’s value to “makeunique” and ColdFusion will automatically resolve name conflicts. Make sure you use the ‘serverFile’ field of the resulting struct to get the name as it was saved.

By: tim

tim — Thu, 22 Dec 2011 23:37:49 +0000

@raffael – one solution I like is to rename the .jpg to the primary key of the record / profile it’s associated with. eg: 1.jpg, 2.jpg. or this could be some other unique identifier. I agree that doing a fileExists() would be a good addition before before writing with cfimage.

By: Raffael

Raffael — Sun, 24 Apr 2011 17:22:32 +0000

Great post!
How do you ensure that uploaded files have unique filenames? your solution could get an error when exact filename already exists in the destination="#application.imageDir#/#uploadResult.serverFileName#.jpg" directory (step cfimage/write). as a first step, you make nameconflict="overwrite" in the temp directory, but later on, the serverfilename could be already present in the "real" destination directory. bad though, cffile action="move", cffile action="copy" and cffile action="write" (and cfimage action="write") have no nameconflict="makeunique" attribute. I think we need a kind of cfdirectory check loop for that filename and append a number or so if already exists. or even make a whole new file with createuuid and check that file for existance before moving/writing.
what do you guys think about this?

By: Mike Henke

Mike Henke — Tue, 23 Nov 2010 18:59:37 +0000

You are the MAN!!!

By: Prashant

Prashant — Mon, 15 Mar 2010 09:09:05 +0000

Good post! very helpful

By: funandlearning

funandlearning — Sun, 26 Jul 2009 05:07:04 +0000

Hi Ryan,

This post is really helpful.

Thanks.