Rick Sanders wrote:
> Hi Todd,
>
> I won't run into a valid issue if the file is never uploaded to the server
> in the first place. Basically the user submits the file, before the <cffile>
> action I check the file name and see if it already exists in the database.
> If it does, then I return the error. If it doesn't exist, then go and
> perform the <cffile> action.
>
> There's a way to do this in ASP.net by checking against the name of the file
> field and the http header to grab the file name. I believe the control is
> browser.httpheader {form.fieldname}
>
> Kind regards,
>
> Rick
That is not the way this works, ASP, JSP, PHP, CF, pick your letters,
the file us uploaded to the server FIRST. Then the application server
technology can grab it and do its mojo.
Your ASP example says just that. It gets the file name from the HTTP
header. The reason the file name is in the HTTP header is because the
entire file content is in the HTTP header. If the user uploaded a 15mb
file, the browser has uploaded a 15mb file to the server and there is a
15mb+ HTTP header that ASP is inspecting.
You are talking about how the HTTP client-server | request-response
standard is built. All web application servers use the same HTTP
standard. This behavior is not going to change from one application
server to another.
Ian
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to
date
Get the Free Trial
http://ad.doubleclick.net/clk;160198600;22374440;w
Archive:
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:298206
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
