Some random thoughts;

  • Isn't the file ALREADY placed in a temp folder at the conclusion of the form post process (before CFFILE even touches it)?
  • Did I miss the part where we tested the name of the uploaded file - by direct comparison - at this point?
  • There are three different character set applications going on here: 1) The name may very well contain "the umlaut code" immediately after upload - depending on the charset applied by the submitting page's form tag. W3C states that Only the "post" method (with enctype="multipart/form-data") is specified to cover the entire [ISO10646] character set. 2) But the CFFILE tag could have used a different charset to rename/move it; and finally 3) our own IDE or browser will apply a charset to show us the file name - as we work to debug the issue - which can confuse our diagnostic efforts.

Al

--
--
online documentation: http://openbd.org/manual/
http://groups.google.com/group/openbd?hl=en
 
---
You received this message because you are subscribed to the Google Groups "Open BlueDragon" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to