From: Dave Watts <[EMAIL PROTECTED]>
> > : To do this use you can use the CGI.CONTENT_LENGTH variable ....
>
> > I just had to do this recently. I found the tutorial here.
> > Check it out:
> >
> > http://www.teamallaire.com/tutorials/limitFileUploadSize.cfm
>
> Unfortunately, relying on CGI.CONTENT_LENGTH doesn't prevent a user from
> uploading a file larger than you want to allow, it merely allows you to not
> do anything with that file. By the time that CGI.CONTENT_LENGTH exists, the
> web server has received the HTTP request header and body containing the
> file, I'd think, since both are sent simultaneously. If your concern is that
> someone will attempt to upload an extremely large file as a crude denial of
> service attack, this doesn't address that concern. You'd need some
> client-side logic, using an applet or ActiveX control, to avoid using
> standard HTTP form-based file uploading.
>
I was sure cgi.content_length wouldn't work either, but since I hadn't
tried the method I tested it to get some empirical data.
It is all server side. At least with WebSite, cgi.content_length isn't available
until after the file is transmitted.
It works as far as providing a message client side that the image was too large,
and works server side in that the uploaded file is not transferred from
the NT temp dir to the target dir -- but the file *is* transmitted in whole and
there is nothing that shortens the time getting to the message that the file is
too big.
Still reccomend AppletFile (or any other client side java/javascript solution).
Pan
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
